GCJ Build Problem (CVS)
Bryce McKinlay
bryce@waitaki.otago.ac.nz
Thu Nov 1 13:35:00 GMT 2001
Brad Cox wrote:
> [bcox@linux bcox]$ locate libgcj.so
> /usr/lib/libgcj.so.1
> /usr/lib/libgcj.so.1.0.0
> /usr/lib/libgcj.so
> /usr/local/lib/libgcj.so.2
> /usr/local/lib/libgcj.so.2.0.0
> /usr/local/lib/libgcj.so
> export LD_LIBRARY_PATH="$(GCC)/lib:$(LD_LIBRARY_PATH)" && a.out
>
> IT WORKED!
Yeah, that makes sense. Note that the new libgcj won't conflict with the
Redhat one in /usr/lib, since they have different "soname" (major
version number), but the one in /usr/local/lib will since it has the
same name so the dynamic linker can't tell the difference. "ldd a.out"
will always tell you exactly what library the dynamic linker is going to
use for a given binary.
regards
Bryce.
More information about the Java
mailing list