Re: libz.so.1 conflict/compatibility issue

[Ken Teague <kteague@pobox.com>]

Florian Kulzer wrote:
> [ snip: the config file sets and exports LD_LIBRARY_PATH and other
>   environmental variables. ]
> 
> Have you put the command to source this config file into .bashrc or
> another startup file? 

Yes, I had it in .bashrc and, after removing it, magic began happening
and things work great! :-)

> I would remove that and use a simple wrapper like this:
> 
> #!/bin/sh
> source /usr/local/bin/acusim/LINUX64/V1.7e/script/.acusim-sh
> /path/to/the/command/that/starts/acuSim
> 
> Put the above three lines into a file that you call, for example,
> my-acusim. (Replace the last line with the correct command to start the
> application, of course.) Make this file executable and put it into
> /usr/local/bin (system wide) or ~/bin (only for your user). Then you can
> use the command "my-acusim" to start the programm. It will run with the
> correct environmental variables while the rest of your system should
> remain unaffected.

Awesome!  However, acuSim has a suite of binaries (e.g. acuSim,
acuSolve, acuTrace, etc.) and each of these binaries accept different
args.  All of the binaries are under
/usr/local/bin/acusim/LINUX64/V1.7e/bin.  How can I adapt the script to
handle the various binaries?  Will I have to add a bunch of case
statements?... or is there an easier way?

Regards,
- Ken