Re: <types.h> and other includes
Re: <types.h> and other includes
- Subject: Re: <types.h> and other includes
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Wed, 23 Feb 2005 09:00:48 -0500
- Thread-topic: <types.h> and other includes
Try to use the -aux-info switch. That will tell you what is being
defined/declared and where. Also, you might try -fno-builtin,
-fno-hosted, and/or -ffreestanding. You will very likely get huge
numbers of errors with the last 3, but you might also get some info
about what is going on. See pages 21-22 in the GCC manual, or go to
http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/C-Dialect-Options.html#C-Dia
lect-Options)
Thanks,
Cem Karan
> ------------------------------
>
> Message: 14
> Date: Wed, 23 Feb 2005 00:43:49 -0700
> From: Markian Hlynka <email@hidden>
> Subject: Re: <types.h> and other includes
> To: Jeff Laing <email@hidden>, David Leimbach
> <email@hidden>
> Cc: XCode Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>
> On Feb 22, 2005, at 22:36, Jeff Laing wrote:
>
> >> 1. I had to add #include <stdlib.h> to a file when using the
> >> makefile, because it didn't know what exit() was. Why didn't xcode
> >> have a problem with this? If xcode has a bunch of
> automatic includes,
> >> is it feasible to disable them so I get the same errors
> for inclusion
> >> as I would when running make? And, if this was an xcode thing, why
> >> didn't gcc/make on OS X have trouble with this?
> >
> > My guess is that your project has a pre-compiled header enabled, but
> > your
> > makefiles don't.
> >
>
> I think I know what you mean, but I think I haven't stated things
> clearly:
>
> Xcode:
> Builds fine, no extra includes required
>
> gcc/make OS X
> Builds fine, no extra includes required
>
>
> gcc/mak linux:
> needs extra includes explicitly added.
>
>
> So, if it was just Xcode, I'd say you were right. But, since make
> behave the same way as Xcode on OS X, could this still be a possible
> reason?
>
> As David said:
>
> > Not sure what functions you called but in C all functions without
> > prototypes are
> > assumed to exist and return "int".
>
> > Not sure why u_int16_t would be defined by default... Some
> automatic
> > Framework includes perhaps?
>
>
> I realize that undefined functions get int return types. But, of the
> above configs, it was the linux one that didn't know what 'exit' was.
> It's a little different for the u_int16_t, but even so, I didn't
> include any Frameworks in my OS X makefile... are these
> things included
> automatically?
>
>
> Markian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden