>Ugh. -i is of course the wrong flag, as pointed out in another post.
I take it you meant to say -E . I don't know gcc well enough to know that
you weren't thinking of something else.
All I could get was either the source spit back out with the directives gone
or just the directives but no values shown. I guess I could "plant"
something to see what got included but I specified no tricks...
Because the trick I used was simple enough. I put this in:
message YES_YOU_GOT_HERE
And it produces the message "parse error before YES_YOU_GOT_HERE" when
compiled, which is a good enough trace. It was good enough for me to find
out that the directives were set the way I thought, and to move on ("these
aren't the bugs you're looking for").
Still it's hard to believe no one in the history of gcc ever thought you'd
want to plant an advisory message in your source.
That's OK; I got bigger problems now. Thanks guys for responding.
Barry
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
