This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
- To: ghazi at caip dot rutgers dot edu (Kaveh R. Ghazi)
- Subject: Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
- From: "Philippe De Muyter" <phdm at macqel dot be>
- Date: Sat, 28 Mar 1998 22:39:02 +0100 (MET)
- Cc: egcs at cygnus dot com, ghazi at caip dot rutgers dot edu
> Simple question. Does gcc guarantee that after it diddles with
> the system headers that a stdlib.h exists in some form?
I think the answer is `yes'...
> For target files which include tconfig.h, since we can't check
> autoconf macros, I'd like to hardwire including stdlib.h to possibly get
> prototypes for malloc, et al.
... but the prototypes that did not exist before fixincludes etc are only
defined if either __USE_FIXED_PROTOTYPES__, __cplusplus or __STRICT_ANSI__
are defined. In some objc file, I defined __USE_FIXED_PROTOTYPES__
before including stdlib.h to get the prototypes for malloc and friends.
Philippe