Re: -undef in mig's cppflags

From:

Roland McGrath

Subject:

Re: -undef in mig's cppflags

Date:

Fri, 28 Dec 2001 22:41:28 -0500 (EST)

> Well, another possibility is to just drop the -cc flag, because "gcc -E -x c"
> is the default already (why is it set to cat anyway?).
It's set to cat because we're using migcom on cpp output here. One of the
reasons the hurd makefiles run cpp directly instead of letting the mig
script do it is that the script doesn't (and can't easily) dtrt with
quoting arguments so complex -D arguments work right.
> Yet another possibility would be to leave it "cat" and change mig to not
> have -undef in the cppflags variable, but in default_cpp:
That seems reasonable enough regardless. I made that change.
> A third possibility is to drop the -undef again, because it does not work
> anyway (i386 is still defined to 1 in gcc). Roland, you did this change,
> what do you think?
Harumph. I thought I tested -undef at the time and it dtrt.
I thought some <mach/i386/foo.defs> include got broken if it didn't.