From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT delorie DOT com>, djgpp-workers AT delorie DOT com, bkorb AT sco DOT COM
Date: Thu, 20 Jul 2000 20:03:17 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: GCC headers and DJGPP port
Message-ID: <39775B05.291.1C186DF@localhost>
In-reply-to: <200007201749.NAA09969@indy.delorie.com>
References: <397719F4 DOT 16F8A257 AT sco DOT com> (message from Bruce Korb on Thu, 20	Jul 2000 08:25:40 -0700)
X-mailer: Pegasus Mail for Win32 (v3.12c)
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

On 20 Jul 2000, at 13:49, Eli Zaretskii wrote:

> > Date: Thu, 20 Jul 2000 08:25:40 -0700
> > From: Bruce Korb <bkorb AT sco DOT COM>
> > 
> > The worst one *is* NULL.  The reason is that there are so bloody
> > many platforms out there that define it in all manner of random places.
> > I assume you know that.  GCC has to adapt itself to all these platforms.
> 
> Sorry, I don't see why does GCC need to adapt itself.  Does this need
> arise when building GCC, or when using it (or both)?
> 
> And what problems are caused by the fact that NULL is defined in many
> places?  Are you talking about platforms which don't have NULL defined
> in the usual places, such as stddef.h?  If so, I think the platforms
> which do have NULL defined where it should be, should not be punished
> on behalf of the non-conforming platforms.
> 
> > > Of course, a working fixincludes might circumvent the technical
> > > problems.
> > 
> > I'm ready to help, but I don't have a DOS platform to play on.
> 
> You don't need to have a DOS machine, any Windows 9X or NT machine, or
> even Linux with DOSEmu, will do: DJGPP supports all these platforms.
> You could even try this on Unix, if you only use Posix functions like
> popen, system, and dup.
> 
> Please don't misunderstand me: I'm not saying that you *should* do
> this yourself, I'm saying that you _can_ do this should you wish to.

With native build of gcc-2.95.X for DJGPP fixincludes simply crashes 
as there is no working fork(). Situation is worse when building cross-
compiler for DJGPP target and Linux host. In this case I found that 
fixincludes breaks DJGPP headers. At that time I found that it's easiest 
to disable fixincludes for DJGPP target and avoiding using GCC 
stddef.h and some similar headers. It was ugly hack but it mostly 
worked.

Andris