This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC headers and DJGPP port


> Date: Tue, 18 Jul 2000 20:35:44 +0200
> From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
> 
> I'm not talking about C, I'm talking about C++. If djgpp does not use
> __null for NULL, then it can't have the features that g++ has on other
> systems.

Sorry, my wording was inaccurate and misleading.  The problem is with
C++ programs that include <stdio.h> or <cstdio> (or stddef.h etc.)
after C++ headers such as <libio.h>: these define NULL, and GCC then
complains about its redifinition.

> I'm confused what question you are asking. Are you asking why GCC
> installs its headers?

It seems there has been a misunderstanding; I apologize for whatever
part of it that I'm responsible for.

Yes, the actual problem is that GCC installs its headers in a way that
cause them to be used before the system headers.  A related problem is
that GCC uses its own versions of stddef.h, limits.h, and other
headers instead of the system headers when GCC is built.  We were
worried that using headers that are different from the system headers
might produce buggy GCC binaries, due to conflicts with libc.a against
which the native DJGPP port is linked.

Our impression was that these two issues are connected, and that GCC
wants both to be built and used with its own versions of some of the
system headers.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]