Changes between Version 1 and Version 2 of Ticket #2916, comment 20
- Timestamp:
- 02/25/16 09:06:13 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2916, comment 20
v1 v2 1 1 We'll have to agree to disagree on that, but it's really immaterial. The issue is that the configure script tries to figure out how to call the preprocessor by building a test file, then decides that any output at all is an error. It then defaults to calling /lib/cpp, which is a horrible assumption. All in all, braindead behavior that's not present in modern implementations. 2 2 3 Edit: I'm thinking the cleanest solution for now might be to specifically set CPP to " /usr/bin/gcc -E -w" for configure.3 Edit: I'm thinking the cleanest solution for now might be to specifically set CPP to "gcc -E -w" for configure.