Here's the bottom line: > Is the CFLAGS -no-cpp-precomp the same as the -traditional-cpp flag?
No. -no-cpp-precomp disables the use of the alternative C preprocessor cpp-precomp. -traditional-cpp invokes the GNU preprocessor with options which cause it to behave differently, as per the GCC documentation. -traditional-cpp implies -no-cpp-precomp. So, adding -no-cpp-precomp is redundant when -traditional-cpp is already on. DaR On 3/24/03 2:08 PM, "Dennis Ruffer" <[EMAIL PROTECTED]> wrote: > I tried that this morning and it didn't make any difference. From the docs, > they appear to be the same, but I should see if that is true. > > DaR > > On 3/24/03 3:33 AM, "Jorge Acereda Maci�" <[EMAIL PROTECTED]> wrote: > >> >> On Monday, March 24, 2003, at 02:31 AM, Dennis Ruffer wrote: >> >>> There seems to be something happening with the next OSX developer >>> tools. >>> The big difference that I know about is the use of gcc 3.3. >>> >>> Anyone have any clues? >> >> Have you tried -no-cpp-precomp instead of -traditional-cpp? >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
