public inbox for
help / color / mirror / Atom feed
From: "RenE J.V. Bertin" <>
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under mips-irix-6.3
Date: Fri, 16 May 2003 16:06:00 -0000	[thread overview]
Message-ID: <> (raw)

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

From: "RenE J.V. Bertin" <>
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under
Date: Fri, 16 May 2003 17:57:31 +0200

 On 16 May 2003 14:18:26 -0000, wrote regarding "Re: libstdc++/10801: ld
 bus error on linking .libs/libstdc++ under mips-irix-6.3"
 8-)     On the face of it, this looks like an ld bug rather than
 8-)     a gcc bug.  Do you have any reason for thinking that gcc
 8-)     is at fault here?
 	Well, it is gcc that generates the code, or that passes an option or sequence of options that choke ld (the command line is really quite complex and long). I have never before experienced this. To be sure, I could try to build for mips-sgi-irix5 to get an o32 system. This I managed for gcc 3.2.0 .
 But I agree that it is not sure that it is a gcc bug. I looked for a discussion forum first, and completely overlooked the existence of the (open) mailing list.

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

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