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?

From: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
To: tromey at redhat dot com
Cc: Java Discuss List <java at gcc dot gnu dot org>, Alexandre Oliva <aoliva at redhat dot com>
Date: Wed, 06 Mar 2002 11:20:36 +1300
Subject: Re: printing exceptions?
References: <873czimtqw.fsf@creche.redhat.com> <3C81649B.7000809@waitaki.otago.ac.nz> <87k7sqr62x.fsf@creche.redhat.com>

Tom Tromey wrote:

>I've spent an inordinate amount of time looking at this.  I've rebuilt
>libgcj from scratch 5 or 6 times in the last couple days.
>
>I think the bug occurs here:
>
>    LIBLINK = $(LIBTOOL) --tag=CXX --mode=link $(CXX) -L$(here) $(JC1FLAGS) $(LDFLAGS) -o $@
>
>If I change this to use `--tag=CC', then the bug goes away.
>I have no theory to explain this.
>
>Alexandre, do you have any insight here?
>Is there any reason I shouldn't just make the above change and check
>it in?  This represents a very serious (and weird) regression.
>

Could it be link order? I noticed libtool was adding some "-lgcc_s" type 
stuff to the link lines for the binaries in libgcj. This messes up the 
link order, causing libgcc to be linked after some of the other shared libs.

regards

Bryce.

References:
- printing exceptions?
  - From: Tom Tromey
- Re: printing exceptions?
  - From: Bryce McKinlay
- Re: printing exceptions?
  - From: Tom Tromey

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