This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: this is not a dynamic executable
- From: David Young <dvd at OCF dot Berkeley dot EDU>
- To: Erik Poupaert <erik dot poupaert at chello dot be>
- Cc: java at gcc dot gnu dot org
- Date: Mon, 21 Apr 2003 13:39:04 -0700
- Subject: Re: this is not a dynamic executable
- References: <POEIJGMGPFPGFHAGKFHAKEFBCHAA.erik.poupaert@chello.be>
It does produce, though, a java.lang.ExceptionInInitializerError, at
__clone(/lib/tls/libc-2.3.2.so).
I noticed that the application I'm working with doesn't reference
/lib/tls/libc-2.3.2.so in the app's ldd output.
Maybe we have the same builds of gcj, but apps calling different
libraries?
My application (now back to "--enable-shared") references /lib/tls/libc.so.6
according to "ldd". But that is just a symbolic link to
/lib/tls/libc-2.3.2.so. I wonder why your application doesn't reference it?
My app references a libc-2.3.2.so, but from /lib/i686 rather than from
/lib/tls. "ldd" also shows links to libm.so.6 and libpthread.so.6 from
/lib/i686, and no references to /lib/tls. According to
https://listman.redhat.com/pipermail/phil-list/2002-October/000147.html,
TLS evidently has something to do with Red Hat 9's new NTPL. Would it
make a difference that I'm running a vanilla 2.4.20 kernel -- does this
kernel support NTPL?
-David