Yes, that's a good comment. I guess, that automake takes care for this.
Anyway, this doesn't solve problem with binary distribution.
Thanks
Alex Muntada wrote:
> Pavel Hlavnicka wrote:
> |
> | possible problems: when shared files are not found at run-time, any of
> | the following should help:
> |
> | a) set LD_LIBRARY_PATH to point to /usr/local/lib. You can do it in your
> | startup files (profile, .bash_profile, .bashrc) depending on current
> | situation
> |
> | b) you may run programs requiring sablot libraries (f.e. sabcmd or
> | apache) using a shell script, which defines and *exports* LD_LIBRARY_PATH.
> |
> | c) add /usr/local/lib to the /etc/ld.so.conf file. Then you can run
> | ldconfig (as root). Running this utility is necessary only after
> | installation, 'cos it is usually run during the boot time.
>
> d) use "runtime path" linker flag for shared libs (it's very
> useful on systems which lack ldconfig). The correct flag
> syntax depends on linker, eg:
>
> Solaris ld:
> ld -R/path/to/lib/dir -L/path/to/lib/dir -lfoo ...
>
> Tru64 UNIX ld:
> ld -rpath /path/to/lib/dir -L/path/to/lib/dir -lfoo ...
>
> GNU binutils ld (eg. Linux):
> ld -rpath /path/to/lib/dir -L/path/to/lib/dir -lfoo ...
>
> HP-UX ld (actually, no flag is needed):
> ld -L/path/to/lib/dir -lfoo ...
>
>
> Compilers can be feeded with that flag, of course:
>
> Solaris: cc -R/path/to/lib/dir ...
> Tru64 UNIX: cc -rpath /path/to/lib/dir
> HP-UX: cc ...
>
> GNU CC: gcc -Wl,-rpath,/path/to/lib/dir ...
> (on Linux, Tru64 UNIX, etc.)
>
> gcc -Wl,-R,/path/to/lib/dir ...
> (on Solaris)
>
> HTH,2
>
> Best,
> Alex
>
> --
> Alex Muntada <[EMAIL PROTECTED]>
> www.ac.upc.es/homes/alexm
>
--
Pavel Hlavnicka
Ginger Alliance Ltd.
Prague; Czech Republic
