Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: wje@fir.engr.sgi.com (William J. Earl)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: gcc for Irix.
Date: Fri, 13 Jun 1997 10:50:28 -0700 (PDT)	[thread overview]
Message-ID: <199706131750.KAA09670@yon.engr.sgi.com> (raw)
In-Reply-To: <199706131654.JAA28555@fir.engr.sgi.com> from "William J. Earl" at Jun 13, 97 09:54:57 am

:
:Miguel de Icaza writes:
:...
: >    I am running into a little problem.  The binary gcc that is
: > available on the free software collection is for Irix 5.3 and the
: > include files that are packaged with it are not quite ok for Irix 6.2
:...
:
:      In what way do the 5.3 include files cause problems?
:

[Note: I'm taking care of Miguel in private email]

The headers that come with gcc are:

	1) Only a very small subset of the full set of headers
	   which were preprocessed by gcc 'fix_header' utility.

	2) Correspond to the OS version on which gcc was built
	   which may be incompatible in subtle ways with the
	   runtime libraries on a later OS version.

Since Miguel's Indy is (apparently) a 6.2 IRIX, possibly
without all the necessary header patches, and the gcc he
is trying was built on 5.3, I can see why he has header
problems.

Anyway, don't worry. This is being taken care of.
-- 
Peace, Ariel

WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: gcc for Irix.
Date: Fri, 13 Jun 1997 10:50:28 -0700 (PDT)	[thread overview]
Message-ID: <199706131750.KAA09670@yon.engr.sgi.com> (raw)
Message-ID: <19970613175028.excP-z0aO5yKiPKFYYgZjClzGNYmHyhDVEQTXgP8GlA@z> (raw)
In-Reply-To: <199706131654.JAA28555@fir.engr.sgi.com> from "William J. Earl" at Jun 13, 97 09:54:57 am

:
:Miguel de Icaza writes:
:...
: >    I am running into a little problem.  The binary gcc that is
: > available on the free software collection is for Irix 5.3 and the
: > include files that are packaged with it are not quite ok for Irix 6.2
:...
:
:      In what way do the 5.3 include files cause problems?
:

[Note: I'm taking care of Miguel in private email]

The headers that come with gcc are:

	1) Only a very small subset of the full set of headers
	   which were preprocessed by gcc 'fix_header' utility.

	2) Correspond to the OS version on which gcc was built
	   which may be incompatible in subtle ways with the
	   runtime libraries on a later OS version.

Since Miguel's Indy is (apparently) a 6.2 IRIX, possibly
without all the necessary header patches, and the gcc he
is trying was built on 5.3, I can see why he has header
problems.

Anyway, don't worry. This is being taken care of.
-- 
Peace, Ariel

  reply	other threads:[~1997-06-13 17:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-13 14:55 gcc for Irix Miguel de Icaza
1997-06-13 16:54 ` William J. Earl
1997-06-13 17:50   ` Ariel Faigon [this message]
1997-06-13 17:50     ` Ariel Faigon
1997-06-13 20:37     ` William J. Earl
1997-06-13 20:37       ` William J. Earl
     [not found]       ` <wje@fir.engr.sgi.com>
1997-06-14 15:39         ` Christopher W. Carlson
1997-06-14 17:21           ` Ariel Faigon
1997-06-14 17:21             ` Ariel Faigon
1997-06-14 17:35             ` David S. Miller
1997-06-16  8:02               ` Martin Knoblauch
1997-06-16 11:42                 ` Ralf Baechle
1997-06-16 11:42                   ` Ralf Baechle
1997-10-01 15:56         ` IRIX ELF docs Christopher W. Carlson
1997-10-01 17:20           ` Ariel Faigon
1997-10-01 17:20             ` Ariel Faigon
1997-10-01 23:28             ` Ralf Baechle
1997-10-02  9:38               ` Martin Knoblauch
1997-06-16  7:30 ` gcc for Irix Martin Knoblauch
  -- strict thread matches above, loose matches on Subject: below --
1997-09-30 23:36 IRIX ELF docs Ralf Baechle
1997-09-30 23:42 ` William J. Earl

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=199706131750.KAA09670@yon.engr.sgi.com \
    --to=ariel@yon.engr.sgi.com \
    --cc=ariel@sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=wje@fir.engr.sgi.com \
    /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