public inbox for
help / color / mirror / Atom feed
From: Richard Sandiford <>
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under mips-irix-6.3
Date: Sat, 17 May 2003 08:06:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR libstdc++/10801; it has been noted by GNATS.

From: Richard Sandiford <>
To: "RenE J.V. Bertin" <>
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under mips-irix-6.3
Date: 17 May 2003 08:54:14 +0100

 "RenE J.V. Bertin" <> writes:
 > The linker crashes when I issue the -s option
 > in the build command.
 Hmm, this sounds similar to a bug mentioned here:
     Ld32 seg fault when linking g++ objects.
     When the latest g++ 2.8.1 is used with the latest 7.2.1
     SGI back-end (assembler/linker/strip) any invocation of
     g++ with the '-s' (strip) option seems to cause a SEGV
     in ld32.  This has been fixed (630196).
 I suggest you try patching or upgrading your linker.
 Alternatively, binutils 2.14 is likely to be released in the next
 couple of weeks and it should handle n32 & n64 much better than
 previous versions.  You could try using that.  (HJ's
 version is out now and may work OK.)
 Using binutils is obviously more bleeding edge, though.  I can't
 guarantee it'll work.
 > Things work fine when I do not do that. To me, this does
 > suggest that gcc does something wrong somewhere when it
 > invokes the linker.
 There doesn't seem to be anything wrong with the failing
 command line.  And if, as you say, removing -s causes the
 link to succeed, I really do think that this is a linker bug.

             reply	other threads:[~2003-05-17  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  8:06 Richard Sandiford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-18  7:03 rsandifo
2003-05-16 16:16 RenE J.V. Bertin
2003-05-16 16:06 RenE J.V. Bertin
2003-05-16 14:18 rsandifo
2003-05-15 13:06 rjvbertin

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:

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

  git send-email \ \ \ \ \

* 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).