Re: Why is thread-for-install considering two identical options?
Steven Watanabe via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Organization | Providere Consulting, Inc. |
| Message-ID | <[email protected]> |
AMDG On 09/22/2018 09:16 PM, Kuhl, Brian via Boost-build wrote: > I'm not sure why I get this new error? > All I did was move a few of the parameters I invoke b2 with into a project-config.jam as requirements. > > project : requirements > <snip> > <threading>multi > <snip> > error: No best alternative for ./thread-for-install > next alternative: required properties: <abi>sysv <binary-format>elf <target-os>vxworks <threadapi>pthread <threading>multi > matched > next alternative: required properties: <abi>sysv <binary-format>elf <target-os>vxworks <threadapi>pthread <threading>multi > matched > This is a bug in the handling of target alternatives. Only one of these should have <threading>multi... except that it was inherited from your project-config.jam, making them identical. Workaround: put the non-conditional requirements in the default-build, instead of the requirements. In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build