Subject: Re: [Boost-build] Effect of usage requirements vs. default values of a feature
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-04-16 12:12:49
On 04/16/2011 08:13 AM, Gevorg Voskanyan wrote:
> Perhaps I'm touching an old ground, but let's consider the following case:
> lib a : a.cpp : <threading>multi : : <threading>multi ;
> exe e : e.cpp a ;
> bjam -n -a gives the output contained in bjam-n-a.log
> Basically there is no -pthread passed when building 'e', even
> though threading-multi is contained within the path to the produced binary.
> bjam -a --debug-building gives the output contained
> in bjam-a--debug_building.log
> Which shows e's build properties to contain both <threading>single and
> <threading>multi, resulting in undefined reference to `pthread_create' link
> How is it possible for a non-free feature to have more than one value for a
> given target? Is this example supposed to work?
Unfortunately, you aren't allowed to put
non-free features in usage-requirements.
I'd like it to work, but I'm not sure how
to specify exactly what the behavior should
be in all cases.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk