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 16:07:32 -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 #20 from bugzilla-gcc at thewrittenword dot com 2005-11-14 16:07 -------
(In reply to comment #19)
> Yes, I checked the installed libgcc_eh.a
> (lib/gcc/ia64-hp-hpux11.23/3.4.5/libgcc_eh.a and
> lib/gcc/ia64-hp-hpux11.23/3.4.5/hpux64/libgcc_eh.a) and both contain
> eh_dummy.o. I do not getting any warnings messages from ld when compiling and
> linking C or C++, with or without -mlp64 and with or without -shared.
Odd. We have the latest linker patch installed on our system (PHSS_33349) and
applying Eric's patch added eh_dummy.o to libgcc_eh.a but the linker still gave
a warning. I guess 'struct eh_dummy;' didn't add enough symbolic information to
the archive library. Change it to 'int __libgcc_eh_dummy;' worked for us.
Looking at Zack's patch, I don't see how eh_dummy.o would get added to
libgcc_eh.a on gcc-3.4 without adding it to $libgcc2_eh_static_objs.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24718