Apparently, and if I understand correctly, the older versions of the sdk (including 1.4.0) used functions in libc that was not part of the "public" API. Therefore, I assume this should be fixed by Blackdown/Sun also for 1.3.1 releases, not just 1.4.1. Note I didn't bother reporting this to either Blackdown or Sun, since I'm happy using 1.4.1, but probably somebody already did. See link below for more details.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=165352&repeatmerged=yes - Hein On Fri, 2002-10-25 at 10:17, David Shepherd wrote: > I'm curious as to what the long term solution to this problem is. > > Does libc need patching to make j2sdk1.3 work again? > > Does j2sdk1.3 need fixing and recompiling? Is this a job for Blackdown > or the Debian packager? > > I downgraded to libc 2.2.5 (from testing) but at least 6 other packages > in unstable require a later version then the testing version. So I > don't feel happy using the downgraded libc for long. > > Dave > > > Hein Meling wrote: > > Well, since you say that you cannot upgrade to 1.4.1 your only choice > > seems to be to downgrade your libc to version 2.2.5. Alternatively, > > maybe you could adhere to the new interface in java.sql.Connection? > > > > - Hein > > > > On Wed, 2002-10-23 at 06:16, Rupa Schomaker wrote: > > > >>-----BEGIN PGP SIGNED MESSAGE----- > >> > >>When ant kicks off a sub process I get the following error. Ant then > >>hangs. > >> > >>/usr/lib/j2sdk1.3-bd/bin/i386/native_threads/java: relocation error: > >>/usr/lib/j2sdk1.3-bd/jre/lib/i386/libjava.so: symbol __libc_waitpid, > >>version GLIBC_2.0 not defined in file libc.so.6 with link time reference > >> > >>I get this both with the pre-packaged debian package and with a > >>version made using mpkg-j2sdk. > >> > >>I would try Sun's 1.4 but the project I'm working on is "incompatible" > >>with 1.4 (interface change in java.sql.Connection). > >> > >>Suggestions? > >> > >>- -- > >>- -rupa > >> > >>-----BEGIN PGP SIGNATURE----- > >>Version: 2.6.3ia > >>Charset: noconv > >>Comment: Processed by Mailcrypt 3.5.7, an Emacs/PGP interface > >> > >>iQEVAwUBPbYifHHDM4ucEopdAQH9rggAjao8Xz1Asf0HE+faGLLZtVrzLvuR7VqQ > >>3hMJzy74BECRlmG6bN/P0cvoclvkFuuYnJScG1BUx0CFLTM9q6XD7wE0YcWqZnVc > >>WNNeej5gmg8QL90hmG4ZC5QnCFfIzQYcGPTpgIo8VXYT+TzBrr+/dQ3msdfUQfck > >>8imCerIEg2mawuZNX82aZnZ7Cq/YOiH+n9EO1Bmp08vjt3JZg278rHclVXRTzN7d > >>8IAgp9+Ys8R031DMig695kHzV8izUKRTsNgacxXQ0FR46kGIKl6zS6Brt18sEw8m > >>yUAeHT+naXNLkA0KQWUsTNVNA8kGZVb8hf0b+92RUmRzqZB3C1jRHw== > >>=yMXa > >>-----END PGP SIGNATURE----- > >> > >> > >>-- > >>To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > > > > -- > David Shepherd > Practiv Applied Software Limited > email: [EMAIL PROTECTED] > phone: +44 130 665 3965 > mobile: +44 7900 682 815 > > ____________________________________________________________________________ > > This e-mail (and any attachments) may contain privileged and/or confidential > information. If you are not the intended recipient please do not disclose, > copy, distribute, disseminateor take any action in reliance on it. > > If you have received this message in error please reply and tell us and then > delete it. Should you wish to communicate with us by e-mail we cannot > guarantee the security of any data outside our own computer systems. > > For the protection of Practiv's systems and staff, incoming and outgoing > emails are automatically scanned. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
