Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
On Thursday 13 February 2003 21:12, Ulf Kister wrote: Hi Paul, Paul de Vrieze [EMAIL PROTECTED] writes: Your installer is actually a binary, not java. Apparently something is wrong with it. I can not diagnose the problem though on this data. Maybe an ldd will work No not exactly - it's a shell script (yes, I forgot to mention this), and unfotunately ldd cannot handle such. Thank you anyway! 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 Paul -- Paul de Vrieze Researcher Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net msg01358/pgp0.pgp Description: signature
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
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
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
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
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
On Friday 14 February 2003 14:08, Ulf Kister wrote: 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. Try installing lib-compat (that includes gcc-2.95.3 libraries) I will report the results for the sake of avoiduing others sticking in the same trap. That would be usefull Paul -- Paul de Vrieze Researcher Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net msg01371/pgp0.pgp Description: signature
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
Hi Paul, Paul de Vrieze [EMAIL PROTECTED] writes: Try installing lib-compat (that includes gcc-2.95.3 libraries) That is exactly what I did in the meantime (while j2sdk still compiles) and what set things straight. I will report the results for the sake of avoiduing others sticking in the same trap. That would be usefull Done. There is just one probably stupid question left to me: Is there another way of finding this (that includes gcc-2.95.3 libraries) out than emerging it? From FreeBSD's ports collection I am used to having a file pkg-plist (stands for packlist or so) around iwith each port which contains information about which files are going to be installed where. So, if trapped in a missing library problem, one could still just grep through the pkg-plist files in the complete ports collection and have good chances to find the corresponding port. I see that the USE-mechanism of gentoo, together with the fact that different versions are available for one port makes this impossible here, but something with similar functionality would be *really* helpful (if it is not already there) for newbies like me. Could be as well a web search database... Anyway: Thanks-a-lot to you all for helping me! Regards, Ulf -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
On Friday 14 February 2003 17:46, Ulf Kister wrote: There is just one probably stupid question left to me: Is there another way of finding this (that includes gcc-2.95.3 libraries) out than emerging it? Ask on this list ;-) From FreeBSD's ports collection I am used to having a file pkg-plist (stands for packlist or so) around iwith each port which contains information about which files are going to be installed where. Maybe this could be extracted from the GRP packages. It can never be a full list though, but as an indication it could work. Paul -- Paul de Vrieze Researcher Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net msg01397/pgp0.pgp Description: signature
Re: [gentoo-user] jalbum3.2 on gentoo1.4 rc2 with sun jdk1.4
On Thu, 2003-02-13 at 19:06, Ulf Kister wrote: Did anyone else encounter this problem and, hopefully, solve it? I guess it's the old Red Hat workaround. Look through the installer shell script for the line LD_ASSUME_KERNEL=2.2.5 and replace the initial L with a #. After that it should work. Two things to note: You may need to use sed to replace it, since some text editors can't handle the ascii encoded data in those installers. vim, for example, messed up one such file for me Second, if this is a standard case, you will need to replace the L in LD with a #. It's not enough to simply add it at the start of the line, since the unpacking algorithm has the offset of the data hardcoded. HTH Anders -- [EMAIL PROTECTED] mailing list
