SGI: Development

compiler-preprocessor disagreements

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8449 notes
Wrote the following at March 3, 2013, 11:06 p.m...
Doesnt seem to hurt anything but just out of curiosity, what causes this ?
Code:
checking fontconfig/fontconfig.h usability... yes
checking fontconfig/fontconfig.h presence... no
configure: WARNING: fontconfig/fontconfig.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: fontconfig/fontconfig.h: proceeding with the compiler's result
checking for fontconfig/fontconfig.h... yes
checking for FcConfigCreate in -lfontconfig... yes


How can fontconfig.h be usable but not present ?
jpstewart
Who joined Sept. 21, 2010, 2:31 p.m.
and authored 165 notes
Wrote the following at March 4, 2013, 7:26 a.m...
Do you have settings for CFLAGS and/or CPPFLAGS?

My guess (and it's just a guess at this point) is that you've got -I/some/path in your CFLAGS so that the compiler can find the file, but that it's not in your CPPFLAGS so that the preprocessor (when run alone) cannot find it. If you move -I/some/path to CPPFLAGS instead, you'll get the expected results.

That's certainly (IMHO) the most likely reason for the compiler and preprocessor to disagree.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8449 notes
Wrote the following at March 4, 2013, 7:44 p.m...
jpstewart wrote:
Do you have settings for CFLAGS and/or CPPFLAGS?

My guess (and it's just a guess at this point) is that you've got -I/some/path in your CFLAGS so that the compiler can find the file, but that it's not in your CPPFLAGS so that the preprocessor (when run alone) cannot find it.

ho ho ! Close inspection revealed a fat-finger typing error in the environment ! Thanks, jp, that solved it.