Re: GCC headers and DJGPP port

[Eli Zaretskii <eliz at delorie dot com>]

> Date: Mon, 17 Jul 2000 23:02:50 +0200
> From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
> 
> GCC needs to know exactly what size_t and wchar_t is

This knowledge is accessible to GCC at build time, in the system
headers.

> NULL is defined as __null on all platforms now

Not in DJGPP.  __null causes trouble in C programs.

> there is no question *that* gcc must know about
> these types even without seeing a single target header file.

Why does it need to know that without seeing target header files?  We
are talking about a native build, not a cross build.

The issue that started this thread is that the DJGPP maintainers don't
understand the _technical_ reasons why should there be any need for
GCC to insist on its own, possibly incompatible, definitions.  That is
what we are asking to explain.  It is most probable that, once we
understand the technical issues involved, a number of plausible
solutions could be suggested.

And yes, we did read all the threads in GCC archives that appear to be
relevant, and we did discuss them at length.  But we still do not
understand the technical considerations that caused GCC to insist on
installing its own headers.  Please help us understand this.