On Freitag 06 Juni 2008, Sergey Plis wrote: > > In general, the depends word is a workaround. > > Thanks for your replies. I do not agree with this statement though. > The example is again is gsl where it is up to the user to decide > which BLAS library to use without recompiling the complete gsl suite. > Thus depends allows me to link libgsl with whatever BLAS > implementation I choose to use, at least in theory.
Yes, in theory. Do you know if this is supposed to work with the dynamic
linker alone, or that it requires static linking, too?
> Your suggestion with environment virable seems not to reveal anything
> :( export LD_BIND_NOW=yes
> bigforth -v -v -v
>
> ... wait for start
>
> include atlas.fs
> Open dynamic library liblapack.so
> liblapack.so Library not found!
>
> The same run with strace gives me:
>
> open("~/soft/lib/liblapack.so", O_RDONLY) = 5
> liblapack.so Library not found!
Seems to be that this liblapack.so is not a "good" shared library -
dlopen tries to load it, finds the file, but finally fails. Either it
depends on something it doesn't tell you, or it's split up into a
shared part and a to-be-linked part. The C linker can select the
correct parts (i.e. if you link with -llapack, it will look for both
liblapack.a and liblapack.so, and if a symbol is only in liblapack.a,
this one will be taken).
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
signature.asc
Description: This is a digitally signed message part.
