Robert, thank you for your suggestions. I too need to use the mklink /D trick to shorten the path names.

On Sat, Jan 12, 2019 at 2:39 AM Robert via Boost-build <> wrote:
On 1/8/2019 11:01 PM, Ben Ernst via Boost-build wrote:
> I am completely unable to build Boost libraries. I have been building on
> this same computer for many years, so this issue is confounding to me.
> I'm posting here in the hope that this peculiar error message might ring
> a bell with someone.
> After bootstrapping, when executing "b2.exe", before getting into the
> actual build (which fails), these error messages are repeated multiple
> times:
>     error: No best alternative for ./headers
>          next alternative: required properties: (empty)
>              matched
>          next alternative: required properties: (empty)
>              matched
> I have attached console output from the offending build.
> My actual command line is:
>     .\b2 -j8 toolset=msvc-14.1 --build-type=minimal --without-mpi
>     --without-python address-model=32 link=shared threading=multi
>     runtime-link=shared windows-api=desktop stage

Hello Ben,

I have not observed this error before.  However, I always surround the
toolset value with quotes.  AFAIK, it is not supposed to matter, but ...


Additionally, I suppose it is possible the b2 .cmd files located inside
the %localappdata%\temp directory have inconsistent content.  The file
names I see on mine for msvc-14.1 are named:


With Visual Studio 2017, the paths are quite long.  What I have to do is
use a very short starting point with the mklink /D option (e.g. C:\v7).
The C:\v7 starts at:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise

I create a build forum post with more details using the Windows Intel
compiler back on June 23, 2017, 11:47 am.  It might be a good reference.
  I hope this helps.



> Thanks in advance!
> _______________________________________________
> Unsubscribe & other changes:

Unsubscribe & other changes: