public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/31577] mipsel-elf fails to build on Solaris 10
Date: Thu, 31 Jan 2008 22:56:00 -0000	[thread overview]
Message-ID: <20080131223552.30436.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31577-13718@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rsandifo at gcc dot gnu dot org  2008-01-31 22:35 -------
"thomas at maier-komor dot de" <gcc-bugzilla@gcc.gnu.org> writes:
> ------- Comment #3 from thomas at maier-komor dot de  2008-01-31 22:18 -------
> Subject: Re:  mipsel-elf fails to build on Solaris 10
>
> rsandifo at gcc dot gnu dot org schrieb:
>> ------- Comment #1 from rsandifo at gcc dot gnu dot org  2008-01-25 10:08 -------
>> I'm not sure how we can make progress on this.
>> It almost seems like the compiler has been miscompiled.
>> 
>> What CC is cc: SUN's compiler or gcc?
>> 
>> 
>
> I've seem to have missed --disable-libssp. Using this configure flag,
> gcc-mipsel compiles with Sun's native cc.

Glad to hear it, and thanks for reporting back.

For the record, (in response to comment #2) there isn't a --disable-lib
option; --disable-lib would just get silently ignored.  I'm not sure if
your message above meant that you'd misspelt --disable-libssp as
--disable-lib or whether it meant that you were now using both
options together.

Also, if you want to build gcc and libgcc without building anything
else, you can use "make all-gcc" and "make install-gcc" instead of "make"
and "make install".  (In 4.3, you need "make all-gcc all-target-libgcc"
and "make install-gcc install-target-libgcc" instead.)  I realise that
what you've got now is probably more convenient though.

Anyway, it sounds like things are working now, so I'll go ahead and
close the bug.  Feel free to open a new one (or reopen this one)
if you think I've done wrong.

Richard


-- 

rsandifo at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31577


  parent reply	other threads:[~2008-01-31 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 12:58 [Bug bootstrap/31577] New: " thomas at maier-komor dot de
2008-01-25 10:47 ` [Bug bootstrap/31577] " rsandifo at gcc dot gnu dot org
2008-01-31 22:22 ` thomas at maier-komor dot de
2008-01-31 22:26 ` thomas at maier-komor dot de
2008-01-31 22:56 ` rsandifo at gcc dot gnu dot org [this message]
2008-01-31 22:56 ` thomas at maier-komor dot de
2008-01-31 23:00 ` rsandifo at nildram dot co dot uk
2008-01-31 23:10 ` thomas at maier-komor dot de

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=20080131223552.30436.qmail@sourceware.org \
    --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).