This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Unsuccessful build of gcc-2.95.1
- To: David dot Billinghurst at riotinto dot com dot au
- Subject: RE: Unsuccessful build of gcc-2.95.1
- From: Erik Mouw <J dot A dot K dot Mouw at its dot tudelft dot nl>
- Date: Fri, 3 Sep 99 23:28:59 +0200
- Cc: gcc at gcc dot gnu dot org
- Organization: Eric conspiracy secret labs
On Thu, 02 Sep 1999 03:09:26 +0000, RTD wrote:
> I can confirm this for MipsPro cc 7.2 and 7.2.1
I can't. A build on an Octane MXI running IRIX 6.5.3 using MipsPRO C 7.2.1
compiled a clean (although not yet heavily tested) gcc-2.95.1. AFAIK every
MipsPRO compiler comes with an o32 backend.
Erik
>> -----Original Message-----
>> From: N8TM@aol.com [SMTP:N8TM@aol.com]
>> Sent: Thursday, 2 September 1999 10:57
>> To: gml4410@ggr.co.uk; gcc@gcc.gnu.org
>> Subject: Re: Unsuccessful build of gcc-2.95.1
>>
>> In a message dated 9/1/99 1:16:54 PM EST, gml4410@ggr.co.uk writes:
>>
>> > This is for mips-sgi-irix6.5 (claimed successful).
>> >
>> > The problem is in the configure stage.
>> >
>> > The config/mh-irix6 tries to set "CC = cc -32" (to avoid n32/n64
>> ABI
>> > problems).
>> The lazy way is to set the environment variable CC='cc -n32' while using
>> MipsPro cc as a bootstrap compiler. AFAIK this works for MipsPro versions
>>
>> since 7.2. Perhaps it's time to change a default configuration which
>> caters
>> for the time before there was a working MipsPro compiler for n32/64. The
>> shoe probably is on the other foot now and 'cc -o32' may be less reliable.
>>
>> Tim
>> tprince@computer.org
>
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2785859 Fax: +31-15-2781843 Email J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/