Re: Re: cc and gcc 3.1 strangeness
Re: Re: cc and gcc 3.1 strangeness
- Subject: Re: Re: cc and gcc 3.1 strangeness
- From: Tom Wetmore <email@hidden>
- Date: Wed, 16 Jul 2008 16:34:00 -0500 (CDT)
Sterling,
It is a little weird. The error message is coming because a real, honest to God C file is being compiled. The name of that C file is very probably lex.yy.c, so you should be able to find that file in your directory. However, the compiler is telling you to look back in the lex file at line 33 to see where the error originated. You are "supposed" to fix the error at line 33 in the lex file and then rerun the lex (or flex, the public domain alternative) to get a new copy of lex.yy.c, and then rerun the compile step again.
In theory. However, if you don't have a lex program or you are unsure of what's going on, you can actually look into the c file, probably lex.yy.c, look for a line something like this:
#line lex.l 33
and you will be in the REAL C file at the REAL SITE of the REAL error. It can be a pain, but there is reason to the madness.
Best of luck.
Tom Wetmore
>From: Sterling Garwood <email@hidden>
>Date: 2008/07/16 Wed PM 05:13:18 EDT
>To: Tom Wetmore <email@hidden>
>Subject: Re: cc and gcc 3.1 strangeness
>so the error message "lex.l line 33 error,,,,,," really is from the c
>file? Is cc actually running lex?
>Thanks for the help ... I was tearing my hair out !!!!
>
>
>On Jul 16, 2008, at 4:59 PM, Tom Wetmore wrote:
>
>> The lex file is not being run through the compiler. The c file
>> generated by lex is. The messages look like they come from a lex
>> file, but that is only to help you go to the line in the lex file
>> that has the error or warning.
>>
>> yacc acts the same.
>>
>> Tom Wetmore
_______________________________________________
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