From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: ariel@sgi.com
Cc: carlson@heaven.newport.sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: gcc for Irix.
Date: Sat, 14 Jun 1997 13:35:26 -0400 [thread overview]
Message-ID: <199706141735.NAA04790@jenolan.caipgeneral> (raw)
In-Reply-To: <199706141721.KAA12726@yon.engr.sgi.com> (ariel@yon.engr.sgi.com)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
Date: Sat, 14 Jun 1997 10:21:07 -0700 (PDT)
And finally there's "fix_headers" - the utility that comes with gcc
and fixes headers so they can be used with some gcc conventions and
extensions to C. Combine this with our multi-standard headers
which I suspect the designers of "fix_headers" never thought of and
you get a pretty cool mess :-)
Which is why in gcc-2.8.0 a completely new fix_headers.irix will exist
which handles it all properly...
next prev parent reply other threads:[~1997-06-14 17:41 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
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 [this message]
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=199706141735.NAA04790@jenolan.caipgeneral \
--to=davem@jenolan.rutgers.edu \
--cc=ariel@sgi.com \
--cc=carlson@heaven.newport.sgi.com \
--cc=linux@cthulhu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.