This is the mail archive of the
mailing list for the GCC project.
Re: Patch for `Shouldn't fixincludes remove assert.h instead of trying to fix it?'
- To: Manfred Hollstein <manfred at s-direktnet dot de>
- Subject: Re: Patch for `Shouldn't fixincludes remove assert.h instead of trying to fix it?'
- From: Jim Wilson <wilson at cygnus dot com>
- Date: Thu, 19 Mar 1998 15:33:54 -0800
- cc: egcs-bugs at cygnus dot com, Manfred dot Hollstein at ks dot sel dot alcatel dot de
* Makefile.in (stmp-fixinc): Copy our own assert.h into the
fixed include directory.
I think this should only be done if FIXINCLUDES != Makefile.in as I
explained in my previous message.
(stdlib.h): Create missing stdlib.h on m68k-motorola-sysv.
In answer to your earlier question, ISO C says that both stdlib.h and
stddef.h must define size_t. There are a number of macros and types that
are defined in more than one place.
Rather than just include stddef.h in stdlib.h though, we could avoid possible
namespace problems by just including the parts that we need. If you something
They we just get the size_t definition that we need and nothing else.
If fix-header is creating the stdlib.h file, perhaps we should patch fix-header
so that it creates the file correctly?
* fixincludes (assert.h): Don't even try to fix a system's
probably broken assert.h - we provide our own.
One of the rules that you are deleting affects two files: assert.h and
sys/mman.h. Are you sure that the sys/mman.h change is no longer needed?
I suspect that you should leave the rule in, and just delete the assert.h
file from the list of filenames for that rule.