This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
- To: eliz at is dot elta dot co dot il
- Subject: Re: GCC headers and DJGPP port
- From: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Date: Tue, 18 Jul 2000 21:13:22 +0200
- CC: lauras at softhome dot net, mrs at windriver dot com, gcc at gcc dot gnu dot org, djgpp-workers at delorie dot com
- References: <200007180918.FAA06988@indy.delorie.com>
> Is __null a builtin in the C compiler?
Not in the C compiler, only in the C++ compiler
> Anyway, one reason that __null might cause trouble is that it breaks
> previous versions of the library which were compiled with different
> definition of NULL. I think we've been discussing that on the DJGPP
> developers list to death.
And did these discussions come to a conclusion, or did everybody die
before that? If there was a conclusion, can you summarize why __null
might break previous versions of the library?
> > + #undef SIZE_TYPE
> > + #define SIZE_TYPE "long unsigned int"
>
> Do I understand correctly that this should go into GCC distribution?
Yes, in the target header files.
> If so, I don't think I mind too much. It does introduce a dependency
> between the library and the compiler, which is unfortunate. I think
> we need to discuss this on the DJGPP devlopers' list.
It doesn't introduce the dependency, the dependency is already there.
Regards,
Martin