Date: Mon, 17 Jul 2000 15:28:52 -0400
Message-Id: <200007171928.PAA31031@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
CC: gcc AT gcc DOT gnu DOT org
In-reply-to: <39735540.C8BD0707@sco.com> (message from Bruce Korb on Mon, 17
	Jul 2000 11:49:36 -0700)
Subject: Re: GCC headers and DJGPP port
References: <200007171736 DOT KAA29313 AT kankakee DOT wrs DOT com> <39734D95 DOT 6D145F00 AT softhome DOT net> <39735540 DOT C8BD0707 AT sco DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Suppose the GCC-supplied "stddef.h" were to do stuff like:
> ...
> and the DJGPP headers were to do the same?  :-)

If you can guarantee that gcc won't change it's mind *again* I suppose
we could agree on something like this.  Historically, though, I've had
to tweak headers with each gcc release whether I "played by the rules"
or did my own thing.  For a long time, it seemed that gcc was going to
be a moving target no matter what I tried, so I went with the simplest
solution for me.

> But I thought you-all used "fixinc.winnt" anyway?  Since I
> don't have a Windows dev box, I was never planning on touching
> that mechanism.  However, I would work with anyone among the
> djgpp-workers interested in making the fixincl program run
> under Win*.  :-)

Unfortunately, DJGPP is a *dos* program, not a Win32 program.  That
makes things even harder (but not impossible).  We have popen()
and system(), but not fork().