Re: [Boost-build] explicitly-specified values of non-free feature <threading> conflict

Subject: Re: [Boost-build] explicitly-specified values of non-free feature <threading> conflict
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-17 16:16:45

AMDG

On 01/16/2018 10:01 PM, Steve Robbins via Boost-build wrote:
> 
> My tester ("Debian-Sid") stopped working December 22.  It now fails with the following 
> error.  Any idea what it means?  Or where to start looking?
> 

The most likely culprit is
https://github.com/boostorg/build/commit/15c876025afb3caa2961642179b112f0532dcdf1

but that's quite a bit later.

My best guess is that it's related to mpi, since I didn't
test with MPI and most testers are fine.  I'll look into
it ASAP.

> /var/lib/jenkins/jobs/Boost-Testing-master-64/workspace/boost_bb/src/build/feature.jam:
> 779: in expand-composites from module feature
> error: explicitly-specified values of non-free feature <threading> conflict
> error: existing values: multi single
> error: value from expanding  <threading>single : single
> <snip>
> export HOME=`pwd`
> echo 'using mpi ;' > site-config.jam
> 
> python run.py --runner=Debian-Sid --bjam-options=-j4 --toolsets=gcc  --tag=master
> 
In Christ,
Steven Watanabe