Date: Thu, 29 Jun 2006 15:09:23 -0700 (GMT-07:00) From: Randall Hyde <randyhyde@earthlink.net> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-hackers@freebsd.org Subject: Re: FLEX, was Re: Return value of malloc(0) Message-ID: <16887068.1151618963387.JavaMail.root@elwamui-cypress.atl.sa.earthlink.net>
next in thread | raw e-mail | index | archive | help
-----Original Message----- > >How about feeding the C source through the preprocessor, stripping out >the #line directives, compiling it and posting the exact gcc error and >source context. Okay, I'll try that when I get home. But I was kind of under the impression that *GCC* runs the preprocessor on the input, during compilation :-). > >It may be a gcc bug, it may be a HLA bug or it could be an interaction >between the FreeBSD headers and HLA. None of the code listed has *anything* to do with the HLA.FLX source (and certainly nothing to do with the rest of the HLA source code). It is quite possible that some FreeBSD headers conflict with this section of the FLEX output (remember, this is *canned* output code from FLEX, this is not generated in response to any FLEX input code). That's why my original question was so generic and not specific -- this would appear to be a generic problem with using FLEX output under BSD and I thought a quick question would affirm/deny that thought. Cheers, Randy Hyde
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16887068.1151618963387.JavaMail.root>