-
Simon Marlow authored
Don't attempt to discover the exact location of cpp, instead use 'gcc -E'. With the right combination of flags, it seems we can get the same behaviour as calling cpp directly.
a9778107
Don't attempt to discover the exact location of cpp, instead use 'gcc -E'. With the right combination of flags, it seems we can get the same behaviour as calling cpp directly.