public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/5117: irix6.5 bootstrap failure when using SGI's compiler Date: Tue, 08 Jan 2002 12:46:00 -0000 [thread overview] Message-ID: <20020108204602.20137.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/5117; it has been noted by GNATS. From: Reichelt <reichelt@igpm.rwth-aachen.de> To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/5117: irix6.5 bootstrap failure when using SGI's compiler Date: Tue, 8 Jan 2002 21:53:44 +0100 Hi, On 3 Jan, rodrigc@gcc.gnu.org wrote: > Synopsis: irix6.5 bootstrap failure when using SGI's compiler > > State-Changed-From-To: feedback->analyzed > State-Changed-By: rodrigc > State-Changed-When: Wed Jan 2 22:39:17 2002 > State-Changed-Why: > Are you sure that you are bootstrapping with the > IRIX compiler? Some of your config.log looks like it > is trying to use gcc. Yes, I'm quite sure. With gcc 2.95.3 and gcc 3.1 everything works fine. > Did you follow the platform specific notes for IRIX at: > http://gcc.gnu.org/install/specific.html#mips-sgi-irix6 I thought I did, but I forgot to add "--disable-multilib" which explains my problems with the "-lc" flag. With "--disable-multilib" the problems with "-lc" disappear. It was my fault, sorry! > and set your CC environment variable to the full path > of the IRIX compiler, with the -n32 flag? I just said "CC=cc" without the full path. Usually the compiler defaults to "-n32". To be sure, however, I also tried "CC=/usr/bin/cc -n32" with the same result. > Also, do things still work if you remove "-lc" from > SHLIB_LINK in the file gcc/config/mips/t-iris6? That problem was my own fault, see above. So I didn't check this workaround. > If you update fastjar from CVS, I think I fixed those problems. I just did a complete bootstrap of the 3.1 20020107 snapshot. Yes, the fastjar issues seem to be solved! The only problems that still persist are the six wrong entries in auto-host.h. Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5117
next reply other threads:[~2002-01-08 20:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-08 12:46 Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-11 4:43 rodrigc 2002-01-10 2:36 Reichelt 2002-01-08 13:26 Reichelt 2002-01-02 22:39 rodrigc 2001-12-17 1:26 Reichelt 2001-12-14 10:56 rodrigc 2001-12-14 10:51 rodrigc 2001-12-14 8:16 reichelt
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=20020108204602.20137.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).