Re: [Boost-build] find-include adds /usr/include even if compiler does not use that path

Subject: Re: [Boost-build] find-include adds /usr/include even if compiler does not use that path
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-03-20 11:42:06

AMDG

On 03/20/2012 08:23 AM, Jeremiah Willcock wrote:
> On Tue, 20 Mar 2012, Steven Watanabe wrote:
> 
>> On 03/20/2012 07:57 AM, Jeremiah Willcock wrote:
>>> For a cross-compiling build, the compiler will not necessarily use
>>> headers from /usr/include, which means that hard-wiring it in is leading
>>> to (on my system) attempting to use zlib.h even though that file doesn't
>>> exist in the compiler's include path.  Shouldn't the directories to
>>> search be found by running the compiler, rather than some other
>>> mechanism?
>>>
>>
>> Do you mean find-include-path from ac.jam?
>> ac.jam has a number of issues.  I think
>> it's best avoided for now.
> 
> The problem I have in that file is that Boost.Iostreams won't compile
> because of this bug; I don't use ac.jam directly.

I'm not seeing how Iostreams uses this.
libs/iostreams/build/Jamfile.v2 manages
its own search.  I thought ac.jam was
unused, but I'm clearly missing something.

>  Should I just edit
> ac.jam to use the correct path?
> 

If it allows you to build, why not?  It's obviously
not a general solution, though.

In Christ,
Steven Watanabe