This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: printing exceptions?


On Mar  5, 2002, Bryce McKinlay <bryce@waitaki.otago.ac.nz> wrote:

> If I compile gij myself like:

> $ gcj gij.cc -I/home/bryce/cvs/gcc/build/i686-pc-linux-gnu/libjava/
> -I/home/bryce/cvs/gcc/build/i686-pc-linux-gnu/libjava/include
> -I./include/

> then it works fine.

> The difference is that libtool passes an explicit "-lgcc_s -lc
> -lgcc_s" to gcj (or c++?) which changes the link order so that
> libgcc_s is not linked first.

There's no reason to demand libgcc_s to be linked first.  It should
work just the same, since every other library that depends on it
should have it initialized first.

Unless gij itself had not been linked with the shared libgcc itself,
in which case it would have symbols from libgcc that would conflict
with those in the shared libgcc, and things would break.

However, gcj is supposed to link with the shared version of libgcc,
always.  Is this not happening?  What is the link command you get in
each case (please add -Wl,-v to the gcj command lines and compare the
printed link commands)

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]