This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: link problems under darwin5.2
- From: Andreas Tobler <toa at pop dot agri dot ch>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: tromey at redhat dot com, GCC-Java <java at gcc dot gnu dot org>
- Date: Mon, 07 Jan 2002 16:52:48 +0100
- Subject: Re: link problems under darwin5.2
- Organization: zero
- References: <Pine.LNX.4.10.10201071015050.21411-100000@mars.deadcafe.org>
Jeff Sturm wrote:
>
> On Mon, 7 Jan 2002, Andreas Tobler wrote:
> > Do I probably have a defective ar?
>
> ISTR having a similar problem on another project. Since ar could not
> preserve path information (does GNU?), it cannot correctly identify
> duplicate members. So it must always append new members to the archive.
Huh, don't know, but the man page says:
>> Files are named in the archive by a single component, i.e., if a file
referenced by a path containing a slash (``/'') is archived it will be
named by the last component of that path. When matching paths
listed on
the command line against file names stored in the archive, only the last
component of the path will be compared.
<<
So if I understand correctly in my case only the Attributes.o is taken
and not the whole path.
>
> Out of curiousity, what AR_FLAGS does ltconfig give you? Look in
> <build-dir>/<target>/libjava/libtool. Mine has:
>
> # The archiver.
> AR="ar"
> AR_FLAGS="cru"
# The archiver.
AR="ar"
AR_FLAGS="rc"
>
> This seems wrong since we never want to replace archive members. Perhaps
> AR_FLAGS="qu" would be a better choice. (You could experiment with that
> on your darwin build by altering your libtool script, removing libgcj.la
> and rebuilding.)
I'll give that a try!
Thanks,
Andreas