public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24718] Shared libgcc not used for linking by default
Date: Fri, 11 Nov 2005 21:58:00 -0000	[thread overview]
Message-ID: <20051111215837.15198.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24718-6116@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from bugzilla-gcc at thewrittenword dot com  2005-11-11 21:58 -------
(In reply to comment #11)
> I have run into a problem with my testing, the link line looks good but I get
> warnings from the HP linker like:
> 
> ld: (Warning) Cannot load library symbol table in
> /proj/opensrc/sje/test2/gcc-ia
> 64-hp-hpux11.23-std/lib/gcc/ia64-hp-hpux11.23/3.4.5/libgcc_eh.a, it might be
> mis
> sing or corrupted. Skipping library
> /proj/opensrc/sje/test2/gcc-ia64-hp-hpux11.2
> 3-std/lib/gcc/ia64-hp-hpux11.23/3.4.5/libgcc_eh.a.
> 
> because libgcc_eh.a is empty.  For some reason on 3.4 this file is completely
> empty (nm returns nothing) but on ToT the file is mostly empty, but it has
> a symbol table and empty test/bss/data and debug sections in it.  On 3.4 I have
> no symbol table in the file which is why I get the warning message.  I used the
> same binutils for each compiler so I don't know yet why there is this
> difference.
> 

Look at gcc/mklibgcc.in in the 4.0 branch. They add a dummy eh_dummy.o file to
libgcc_eh.a to work around this. We had Eric Botcazou backport it to the 3.4
branch for us but a PR hasn't been created. I don't know if its considered a
safe enough fix. I haven't tested it yet but I'll attach the patch to this PR.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24718


  parent reply	other threads:[~2005-11-11 21:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 19:24 [Bug driver/24718] New: " bugzilla-gcc at thewrittenword dot com
2005-11-08  1:41 ` [Bug target/24718] " wilson at gcc dot gnu dot org
2005-11-08  3:15 ` bugzilla-gcc at thewrittenword dot com
2005-11-08 21:22 ` sje at cup dot hp dot com
2005-11-08 21:49 ` bugzilla-gcc at thewrittenword dot com
2005-11-09  0:34 ` wilson at specifix dot com
2005-11-09  0:47 ` bugzilla-gcc at thewrittenword dot com
2005-11-09  1:45 ` wilson at gcc dot gnu dot org
2005-11-10  0:08 ` sje at cup dot hp dot com
2005-11-10  3:04 ` wilson at tuliptree dot org
2005-11-10 18:20 ` sje at cup dot hp dot com
2005-11-11 21:39 ` sje at cup dot hp dot com
2005-11-11 21:58 ` bugzilla-gcc at thewrittenword dot com [this message]
2005-11-11 22:00 ` bugzilla-gcc at thewrittenword dot com
2005-11-11 22:16 ` wilson at tuliptree dot org
2005-11-11 23:42 ` sje at cup dot hp dot com
2005-11-12  8:17 ` ebotcazou at gcc dot gnu dot org
2005-11-14 15:44 ` sje at cup dot hp dot com
2005-11-14 15:52 ` ebotcazou at gcc dot gnu dot org
2005-11-14 16:01 ` sje at cup dot hp dot com
2005-11-14 16:07 ` bugzilla-gcc at thewrittenword dot com
2005-11-14 16:10 ` ebotcazou at gcc dot gnu dot org
2005-11-14 16:28 ` ebotcazou at gcc dot gnu dot org
2005-11-14 16:33 ` sje at cup dot hp dot com
2005-11-14 16:59 ` bugzilla-gcc at thewrittenword dot com
2005-11-14 17:05 ` sje at cup dot hp dot com
2005-11-14 17:18 ` bugzilla-gcc at thewrittenword dot com
2005-11-14 17:26 ` sje at cup dot hp dot com
2005-11-14 17:29 ` bugzilla-gcc at thewrittenword dot com
2005-11-14 17:31 ` sje at cup dot hp dot com
2005-11-14 17:35 ` sje at cup dot hp dot com
2005-11-14 17:41 ` bugzilla-gcc at thewrittenword dot com
2005-11-14 17:46 ` sje at cup dot hp dot com
2005-11-14 17:51 ` ebotcazou at gcc dot gnu dot org
2005-11-14 17:51 ` bugzilla-gcc at thewrittenword dot com
2005-11-16 17:06 ` sje at gcc dot gnu dot org
2005-12-01 21:03 ` sje at cup dot hp dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051111215837.15198.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).