I want to add that for anyone trying to install jbuilder. The LD_ASSUME_KERNEL was causing problems there too. JBuilder now install and works perfectly thanks.



At 02:08 PM 2/14/2003 +0100, Ulf Kister wrote:
Hi Paul,

Paul de Vrieze <[EMAIL PROTECTED]> writes:

> [ ... ]
>
> My guess it is a binary embedded in the shell script or that it uses a binary
> installer. Shell scripts don't give dynamic linker errors

You guess right. But ldd gives no help here, since it is a compound
problem, as I found out yesterday:

1. The "LD_ASSUME_KERNEL"-Tip from Anders was the first step to
solving it.

2. Then the graphical (!) java based (!!) installer fails - like
another graphical java program I installed for proof - with a
message like

<snip>
java.lang.UnsatisfiedLinkError:
/opt/sun-jdk-1.4.1.01/jre/lib/i386/libfontmanager.so:
libstdc++-libc6.1-1.so.2:
cannot open shared object file: No such file or directory
</snip>

which is no surprise, because I do not have that library.

This is a reminiscence to gcc2.9.x which is assumed to be used by
Sun's binary installations for Linux (They compile their stuff on
RedHat, which is a little more conservative at this point :-).

If you use gcc3.2 to compile your libc graphical java applications
will fail anyway.

The solution is (at least I hope so, because a very reliable friend
told me, but could'nt prove yet because of my poor bandwith) to
compile the JDK with gcc3.2.

I will report the results for the sake of avoiduing others sticking in
the same trap.

Regards and Thanks again, Ulf



--
[EMAIL PROTECTED] mailing list

Felix Rodriguez
Programmer Analyst
Phone: 860-685-3984
Email: [EMAIL PROTECTED]



--
[EMAIL PROTECTED] mailing list

Reply via email to