Re: this is not a dynamic executable

[David Young <dvd at OCF dot Berkeley dot EDU>]

Erik,

Erik Poupaert wrote:

> > > > > > I just compiled 3.3 20030420, whose executables produce the same ldd
> > > > > > output as executables from my 3.3 20030411 compilation made.
> > > > > >            
>
> I can't find 3.3 20030420 on any of the mirrors. Have you just pulled it
> freshly off the branch?
>  

I pulled it off the gcc-3_3-branch on CVS yesterday (April 20) and 
configured it so that "gcc -v" outputs:

Reading specs from /usr/local/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
Configured with: ../gcc/configure --enable-threads=posix 
--prefix=/usr/local/encap/gcc-3.3-20030420-ns --disable-shared 
--enable-languages=c++,java --program-suffix=-3.3-ns
Thread model: posix
gcc version 3.3 20030420 (prerelease)


> Again my mistake. The script also runs on windows, where it automatically
> invokes upx to compress the executables produced. Obviously, ldd doesn't
> recognize the compressed format.
>
> 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?

-David