On Tue, Feb 25, 2003 at 06:10:13PM +0100, Emiliano wrote:
> On Tue, Feb 25, 2003 at 09:21:26AM -0000, [EMAIL PROTECTED] wrote:
>
> > > Does config.log say anything relevant?
> >
> > This is the output of the config.log. I am a bit confused by the messages
> > are saying /usr/local/include is a non-system directory. Could someone
> > point out my mistake?
>
> That message is normal -- anything but /usr/include is non-system.
Incorrect at least for GCC on most Unix-like systems. "info cpp 'search path'"
says:
"GCC looks in several different places for headers. On a normal Unix
system, if you do not instruct it otherwise, it will look for headers
requested with `#include <FILE>' in:
/usr/local/include
/usr/lib/gcc-lib/TARGET/VERSION/include
/usr/TARGET/include
/usr/include
For C++ programs, it will also look in `/usr/include/g++-v3', first. In
the above, TARGET is the canonical name of the system GCC was configured
to compile code for; often but not always the same as the canonical name
of the system it runs on. VERSION is the version of GCC in use."
So, /usr/local/include is treated as system directory for GCC. Bruno
Haible did some work to detect actual case in glibc's m4 macros, we might
look at that code to enhance our ones.
--
/ Alexander Bokovoy
---
RELATIVES!!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
