Re: Errors linking to stdarg.h and float.h
Re: Errors linking to stdarg.h and float.h
- Subject: Re: Errors linking to stdarg.h and float.h
- From: Fritz Anderson <email@hidden>
- Date: Sun, 20 Jun 2010 12:44:47 -0500
On 20 Jun 2010, at 1:02 AM, Jens Alfke wrote:
> I don’t think there’s any such thing as “#include_next”. Do you mean the regular “#include”?
It's a GCC extension. It means "I've replaced this system header with my own, earlier in the search path, but I want to inherit the older one. Do an #include, starting the search at the next directory in the path."
OP — It's a minor point, but precise terms matter: Linking is a separate step that occurs after all your compilation is done. Calling is something you do to some binary code when the program is running. You do not "link" or "call" a source file. You include it.
To condense the OP, he believes his problems are a cascade from:
> In file included from
> /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:12,
> ...
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error:
> stdarg.h: No such file or directory
>
> In file included from
> /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:16,
> ...
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error:
> float.h: No such file or directory
At the lines indicated by the error: messages, /usr/include/stdarg.h and /usr/include/float.h do an #include_next for headers of the same name. The question then becomes, why are neither of those files to be found later in the search paths?
Poking around with Google turns up this compiler option that will make GCC spill the #include paths:
-Wp,v
(note comma and no space). Project > Edit Active Target (opt-cmd-E). Put "-Wp,v" in the "Other C Flags" build setting, taking care that the Configuration: popup shows the configuration you're using now. Clean your target, including the precompiled header. Do a build. In the Build Results window, set the options so that "All Messages" are visible. Select the precompilation step, and note the lozenge with the lines-of-text graphic on it. This will expand the command-line transaction in that step, which will include the #include paths. Send that to this list.
Don't forget to clear out the Other C Flags setting.
— F
_______________________________________________
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