This sounds like a bug in glibc, as I believe that glibc 2.1.3 is supposed to be backwards compatible with earlier versions, for non c++ code. I can update the dependency to use java 1.4, but its probably the case that java 1.4 was compiled with gcc 3.2 and 1.3 wasn't. Can someone on the glibc team take a look at this and see if its an upstream bug in glibc? Apparently, the symbol __libc_recvfrom had the version GLIBC_2.0 in glibc 2.2.5 and in glibc 2.3.1 it has the version GLIBC_PRIVATE. thanks cardenas -- michael cardenas | lead software engineer, lindows.com hyperpoem.net | GNU/Linux software developer people.debian.org/~mbc | encrypted email preferred "The devils of truth steal the souls of the free." - Trent Reznor
Attachment:
pgpMWsFbvGzrS.pgp
Description: PGP signature