Boost logo

Boost-Build :

Subject: [Boost-build] Antw: Re: Boost build failed if custom toolset path is not available
From: marfro (markus.froschauer_at_[hidden])
Date: 2016-02-25 09:22:08

Thank you very much, the provided workaround works for me.

>>> "Steven Watanabe-4 [via Boost]" <ml-node+s2283326n4683758h49_at_[hidden]> 24.02.2016 03:10 >>>

On 02/17/2016 12:49 AM, marfro wrote:
> I am successfully compiling the boost library (1_46_0) for msvc and for gcc.
> For gcc I use a custom toolset path. Therefore I created an entry in the
> user-config.jam file. If that path is not available the whole boost build
> files even when I build it only for msvc.
> After enabling the debug information I see that the build process
> initializes and checks all using statements of the user-config.jam file. Why
> is that necessary, since I already named the toolset on the bjam call?
> Does anybody know if I can avoid this behaviour so the build still be
> successfull even though the path is missing?

  It used to be that this was required to work,
and it still does with some tools, just not gcc.
The easiest workaround is to check whether the
path exists:

import path ;
if [ path.exists /path/to/g++ ]
    using gcc : /path/to/g++ ;

In Christ,
Steven Watanabe

Unsubscribe & other changes:

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from Boost build failed if custom toolset path is not available, click here
( .

Wittmann Kunststoffgeraete Ges.m.b.H.
A-1220 Wien
Geschaeftsfuehrer: Dr. Werner Wittmann
FN 101312p, Handelsgericht Wien

This e-mail message has been scanned for Viruses and Content

View this message in context:
Sent from the Boost - Build mailing list archive at

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at