This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49992] lto-bootstrap reveals duplicate symbols on x86_64-apple-darwin11
- From: "iains at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 12 Aug 2011 08:51:32 +0000
- Subject: [Bug target/49992] lto-bootstrap reveals duplicate symbols on x86_64-apple-darwin11
- Auto-submitted: auto-generated
- References: <bug-49992-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49992
--- Comment #49 from Iain Sandoe <iains at gcc dot gnu.org> 2011-08-12 08:51:32 UTC ---
(In reply to comment #47)
> (In reply to comment #43)
>
> > Changing the topic to target - although there's a latent issue with the two
> > diagnostic implemenations, (and I will post comment 6, when the reg-tests are
> > done on linux) the actual bug is a target one.
> Note that error posted in Comment 41. There are additional duplicated
> symbols in errors.c that conflict with those in diagnostic.c (in that case
> fancy_abort). So if you intend to proceed with the patch in comment 6, it
> should be expanded to address all the duplicated symbols which can potentially
> conflict.
comment 6 does not rename the duplicated symbols. In fact what it does is to
rename "fatal" = > "fatal_error" in the gen* and errors.c, so that it is not
necessary to link errors.o when libcommon.a is available.
Looking at comment 41, it doesn't look as if you had applied comment 6 when the
test was carried out - since the link line includes both errors.o and
libcommon.a.
>Alternative, we can simply drop the use of '-c' with ranlib and be
> done with it.
let's complete the testing on darwin 8 - and, if that is OK, I'll produce a
patch to remove the special casing of ranlib on darwin entirely (as suggested
by Mike).