This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: dependency_libs
- To: Jeff Sturm <jsturm at one-point dot com>
- Subject: Re: dependency_libs
- From: Tom Tromey <tromey at redhat dot com>
- Date: 04 Apr 2001 19:27:43 -0600
- Cc: java at gcc dot gnu dot org, GCC Hackers <gcc at gcc dot gnu dot org>
- References: <Pine.LNX.4.10.10104041612210.17111-100000@mars.deadcafe.org>
- Reply-To: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> Having just updated my tree, I'm finding that libtool is
Jeff> miscompiling gij by linking -lc before -lpthread. Removing -lc
Jeff> from dependency_libs in libgcj.la fixes it so the testsuite runs
Jeff> once again.
I've found similar problems. I looked at the test suite logs and got
the libtool command that linked a program which crashed.
Then I tried compiling it by hand and gradually removed options until
I found what caused the problem. It isn't -lpthread for me though.
If I link with `-lgcc_s -lc', then it works. If I link with just
`-lc' (and the implicit -lgcc_s later on) then it fails.
This explains why I see the failure with exception handling. In the
failing case we're picking up the wrong exception handling routines.
I think this is going to be confusing to anybody who links with `-lc'
on Linux. I know that isn't common practice, but some people do it.
I'm not yet sure what the fix is for Java. I haven't yet looked for
where the `-lc' in the link is coming from.
Tom