This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/31577] mipsel-elf fails to build on Solaris 10
- From: "thomas at maier-komor dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Jan 2008 22:38:27 -0000
- Subject: [Bug bootstrap/31577] mipsel-elf fails to build on Solaris 10
- References: <bug-31577-13718@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from thomas at maier-komor dot de 2008-01-31 22:38 -------
Subject: Re: mipsel-elf fails to build on Solaris 10
rsandifo at gcc dot gnu dot org schrieb:
> ------- 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
>
>
Thanks Richard for the clarifications. All is fine, you can close this bug.
One final question: can you tell me, what libssp is?
Thanks,
Thomas
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31577