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: William DeShazer <email@hidden>
- Date: Mon, 21 Jun 2010 21:50:02 -0400
On Mon, Jun 21, 2010 at 2:00 PM, Fritz Anderson <email@hidden> wrote:
> On 20 Jun 2010, at 11:45 PM, Jens Alfke wrote:
>
>> It looks like “-Wp,v wasn’t the right set of flags; it seems to have confused the compiler.
>
> Drat. It worked for me on GCC 4.2. man gcc does say that -Wp flags are volatile.
Well this is interesting.
After reading the previous post, I opened displayed the Project
"SplitSpeech" Info and cleared the flags out of "Other C Flags". I
then tried -Xpreprocessor -v. When I rebuilt, I got the same result as
I previously posted. I then cleared out the flags from "Other C Flags"
and got the same behavior again! I looked at the build results and
noted that Xcode was continuing to place the -Wp,v flag in the
compilation. Please note, that I clean the targets many times trying
to get it to stop behaving so oddly. After about 40 minutes, I began
looking at other places where I might find these flags being retained.
Finally, I clicked on the Target "SplitSpeech" Info and lo-and-behold
the -Wp,v flags were still there. In other words there was a
disconnect from the project build options and the target build
options. Clean the target did not reset its build options.
So, I cleared the options in the target and I rebuilt and I got back
to where I was at the beginning of the original post.
So, I got a funny feeling that my target was not being cleaned, for
whatever reason. Thus, I deleted it and created a new target. The
default options for the new target were reset to iPhone style options,
so I had to reset them. I only reset 2 options. I change the Target OS
to 10.4 and I reset the GCC version to 4.0. I then rebuilt and bam. No
evil errors. I get a message that the build succeeded.
I have an idea that XCode 3.2.2 was having problems with my target for
some reason and therefore did not properly respond to cleaning
instructions and build instructions. However, I think that my build is
working.
Here is my question. Should we continue to diagnose this or is the
resolution as simple as deleting the old target and creating a new
one? I would be happy to continue until either/both of you felt
satisfied that we have gotten to the root of the problem.
Thanks for everything thus far.
Regards,
Will
_______________________________________________
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