Re: [Boost-build] Build issues with boost/regex and ICU_PATH

Subject: Re: [Boost-build] Build issues with boost/regex and ICU_PATH
From: Steve M. Robbins (steve_at_[hidden])
Date: 2008-10-24 23:29:56

On Fri, Oct 24, 2008 at 08:51:25AM -0400, Alexander Sack wrote:
> On Fri, Oct 24, 2008 at 4:43 AM, John Maddock <john_at_[hidden]> wrote:

> > No it's deliberate: adding /usr/include to the list of include paths breaks
> > most *nix systems, well gcc on Linux anyway.  So any patch has to be BSD
> > specific.
> 
> Wait, /usr/local/include breaks gcc on Linux?  I realize /usr/include
> might but /usr/local/include?

It breaks any GCC, since:

(a) gcc has /usr/local/include on its default include search path, and
(b) specifying -I /usr/local/include means it is on the path twice, so
(c) #include_next doesn't work properly.

At least, that's my recollection of the problem (which was many years
ago on IRIX).  Take it with a grain of salt, since my memory has
recently been shown to be faulty.  :-)

-Steve