This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/24718] Shared libgcc not used for linking by default
- From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Nov 2005 17:18:54 -0000
- Subject: [Bug target/24718] Shared libgcc not used for linking by default
- References: <bug-24718-6116@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #26 from bugzilla-gcc at thewrittenword dot com 2005-11-14 17:18 -------
(In reply to comment #25)
> I build binutils with --disable-shared and using flex/bison instead of
> lex/yacc, that is probably why my ar works. I experimented with the use of the
> system ar/ranlib by just building eh_dummy.o and .a by hand and they look OK to
> me, I.e. they have a symbol table in them and thus should not get the warning
> message.
Ok, I have a working binutils-2.16 ar. And, binutils-2.16 ar creates a
libgcc_eh.a that does not cause linker errors whereas HP as does _not_, with
the _same_ eh_dummy.o file. Replace your libgcc_eh.a in your GCC tree with the
version created by the system ar and I expect you'll see the same as me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24718