public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12611] Gcc doesn't handle SGI's modularized compiler setup
Date: Wed, 12 Nov 2003 21:52:00 -0000 [thread overview]
Message-ID: <20031112215225.24597.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031014025253.12611.rrr6399@futuretek.com>
------- Additional Comments From ro at techfak dot uni-bielefeld dot de 2003-11-12 21:52 -------
Subject: Re: Gcc doesn't handle SGI's modularized compiler setup
> This sounds more like a /bin/sh bug then. Rob, did the build finish when using
> bash? Rainer, have you seen /bin/sh crashes too on Irix? Thanks.
Not on IRIX 6.5 (but I'm usually running recent releases like 6.5.21f
there, though I haven't seen them in 6.5.10m either), but /bin/sh (or even
/bin/ksh) on IRIX 6.2 have sometimes crashed on me. I don't recally the
exact circumstances right now (and cannot bootstrap without bash due to PR
bootstrap/12752 right now).
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12611
next prev parent reply other threads:[~2003-11-12 21:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 2:52 [Bug bootstrap/12611] New: " rrr6399 at futuretek dot com
2003-10-14 3:08 ` [Bug bootstrap/12611] " rrr6399 at futuretek dot com
2003-10-14 3:37 ` pinskia at gcc dot gnu dot org
2003-10-14 4:46 ` rrr6399 at futuretek dot com
2003-10-14 4:49 ` pinskia at gcc dot gnu dot org
2003-10-22 6:06 ` wilson at specifixinc dot com
2003-10-24 23:27 ` dhazeghi at yahoo dot com
2003-10-25 1:39 ` pinskia at gcc dot gnu dot org
2003-10-28 2:50 ` rrr6399 at futuretek dot com
2003-10-28 2:56 ` rrr6399 at futuretek dot com
2003-11-08 21:09 ` dhazeghi at yahoo dot com
2003-11-11 14:09 ` rrr6399 at futuretek dot com
2003-11-12 21:52 ` ro at techfak dot uni-bielefeld dot de [this message]
2003-11-13 1:57 ` rrr6399 at futuretek dot com
2004-01-21 18:19 ` dhazeghi at yahoo dot com
2004-02-21 15:39 ` rrr6399 at futuretek 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=20031112215225.24597.qmail@sources.redhat.com \
--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).