From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: Martin Heller <martin.heller@mems.mheller.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Don't drop GCC on Interix!
Date: Sat, 05 Oct 2002 12:43:00 -0000 [thread overview]
Message-ID: <20021005184203.GB13622@doctormoo.dyndns.org> (raw)
In-Reply-To: <3D9D8648.3020500@mems.mheller.org>
On Fri, Oct 04, 2002 at 02:15:04PM +0200, Martin Heller wrote:
> Don't do it!
> It has not been abandoned ; Don Terry from Interix, now Microsoft, is
> working on it right now - I've got a 3.something working myself.
Then you can probably help me with the files I want to clean up. :-)
config/x-interix: This is one of only two (!) per-host Makefile fragments
remaining; I'm hoping to get rid of the entire infrastructure for this.
Does 3.x work if you blow this away? If not, what needs to be changed?
config/alpha/xm-alpha-interix.h
config/i386/xm-i386-interix.h
I don't know if you're on Alpha or i386, but is there some way to get
these host-side defs out of fragments and into something more generic?
fixinc/fixinc.interix: This is the weirdest one of all. Although it's
a long file, at the moment *all* it does is "rm -f include/stddef.h",
which seems odd at best and dangerous at worst. Does this file need to
exist? Why is it doing what it's doing, anyway?
--Nathanael
parent reply other threads:[~2002-10-05 18:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3D9D8648.3020500@mems.mheller.org>]
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=20021005184203.GB13622@doctormoo.dyndns.org \
--to=neroden@doctormoo.dyndns.org \
--cc=gcc@gcc.gnu.org \
--cc=martin.heller@mems.mheller.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).