public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "RenE J.V. Bertin" <rjvbertin@hotmail.com>
To: rsandifo@sources.redhat.com
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under mips-irix-6.3
Date: Fri, 16 May 2003 16:16:00 -0000	[thread overview]
Message-ID: <20030516161601.15389.qmail@sources.redhat.com> (raw)

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

From: "RenE J.V. Bertin" <rjvbertin@hotmail.com>
To: rsandifo@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, rjvbertin@hotmail.com, rsandifo@sources.redhat.com,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/10801: ld bus error on linking .libs/libstdc++ under
 mips-irix-6.3
Date: Fri, 16 May 2003 18:07:57 +0200

 On 16 May 2003 14:18:26 -0000, rsandifo@sources.redhat.com wrote regarding "Re: libstdc++/10801: ld
 bus error on linking .libs/libstdc++ under mips-irix-6.3"
 
 Sorry:
 
 I see that an addendum I tried to post yesterday bounced.
 I'm using the system ld, version 7.10.
 
 I also just noticed that when I use the resulting build (done throughout with -mips4 -mabi=n32 -mcpu=r5000, and done once more with gcc as the bootstrap), the linker crashes when I issue the -s option in the build command. 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.
 
 R.B.


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 16:16 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: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:
  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=20030516161601.15389.qmail@sources.redhat.com \
    --to=rjvbertin@hotmail.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rsandifo@sources.redhat.com \
    /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).