Re: problem with CFLAGS

[Wayne Davis]

Thanks for the reply.

What's the best way of handling this issue?  I'd rather not have the
users type in /usr/include to reference "standard" headers.

w



> > I'm not sure what to call so that CFLAGS contains system default paths,
> > such as /usr/include.  How do I make sure CFLAGS contains the defaults?
> 
> The right place for -I options is CPPFLAGS, not CFLAGS.
> AC_PROG_CPP and AC_PROG_CC both arrange to have CPPFLAGS propagated.
> 
> However, normally you don't want CPPFLAGS to contain -I/usr/include,
> since this breaks on many systems where GCC wraps system include
> files, e.g. GCC on Solaris.