[boost] mismatched versions of Boost.Build engine and core

[Paul A. Bristow]

I've got this message after running a bjam

warning: mismatched versions of Boost.Build engine and core
warning: Boost.Build engine (bjam) is 03.1.19
warning: Boost.Build core (at I:/boost-trunk/tools/build/v2) is 2011.04-svn

Should I worry about this?

I've tried to re-build using

I:\boost-trunk\tools\build\v2\engine>bjam --toolset=msvc >build_bat.log

but it still complains

### No toolset specified. Please use --toolset option.

Is this supposed to be

--toolset=msvc

or --toolset msvc

Suggestions?

Thanks

Paul

PS This bit of the doc didn't seem right be me

"For the Boost.Jam source included with the Boost distribution the jam
source location is BOOST_ROOT/tools/jam/src."

and was suggesting running build.bat

I:\boost_1_46_0\tools\build\v2\engine\src contained build.bat and build.jam

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB UK
+44 1539 561830 07714330204
pbri...@hetp.u-net.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Edward Diener]

On 4/6/2011 12:57 PM, Paul A. Bristow wrote:
> I've got this message after running a bjam
>
> warning: mismatched versions of Boost.Build engine and core
> warning: Boost.Build engine (bjam) is 03.1.19
> warning: Boost.Build core (at I:/boost-trunk/tools/build/v2) is 2011.04-svn
>
> Should I worry about this?

Just run 'bootstrap' from the tools/build/v2 directory. Make sure the
new bjam generated is somewhere in your PATH.

[Steven Watanabe]

AMDG

On 04/06/2011 09:57 AM, Paul A. Bristow wrote:
> I've got this message after running a bjam
>
> warning: mismatched versions of Boost.Build engine and core
> warning: Boost.Build engine (bjam) is 03.1.19
> warning: Boost.Build core (at I:/boost-trunk/tools/build/v2) is 2011.04-svn
>
> Should I worry about this?
>

Maybe. I've been ignoring it for now.

> I've tried to re-build using
>
> I:\boost-trunk\tools\build\v2\engine>bjam --toolset=msvc>build_bat.log
>
> but it still complains
>
> ### No toolset specified. Please use --toolset option.
>
> Is this supposed to be
>
> --toolset=msvc
>
> or --toolset msvc
>
> Suggestions?
>

toolset=msvc (no --)

>
> PS This bit of the doc didn't seem right be me
>
> "For the Boost.Jam source included with the Boost distribution the jam
> source location is BOOST_ROOT/tools/jam/src."
>
> and was suggesting running build.bat
>

I use build.bat to build bjam.

> I:\boost_1_46_0\tools\build\v2\engine\src contained build.bat and build.jam
>

In Christ,
Steven Watanabe

[Max Sobolev]

On 06.04.2011 21:23, Steven Watanabe wrote:
>
> I use build.bat to build bjam.

Do you know why bootstrap.bat haven't toolset argument that forwards to
build.bat?

Selected build strategy on windows is not well, i think.

* automatic toolset detection should only be given as an option
(maybe keywords 'default' or 'auto' are fit)
* hope to find toolset on its default dir is naive

--
- Do you speak English? Мужик с глубоким вздохом: - Yes I do. А хули толку?

[Paul A. Bristow]

> -----Original Message-----
> From: boost-...@lists.boost.org [mailto:boost-...@lists.boost.org]
> On Behalf Of Edward Diener
> Sent: Wednesday, April 06, 2011 6:19 PM
> To: bo...@lists.boost.org
> Subject: Re: [boost] mismatched versions of Boost.Build engine and core
>
> On 4/6/2011 12:57 PM, Paul A. Bristow wrote:
> > I've got this message after running a bjam
> >
> > warning: mismatched versions of Boost.Build engine and core
> > warning: Boost.Build engine (bjam) is 03.1.19
> > warning: Boost.Build core (at I:/boost-trunk/tools/build/v2) is
> > 2011.04-svn
> >
> > Should I worry about this?
>
> Just run 'bootstrap' from the tools/build/v2 directory. Make sure the new
bjam
> generated is somewhere in your PATH.

Thanks for this.

I've now got

C:\Users\Paul>bjam --version
Boost.Build 2011.04-svn

and no worrying warnings.

But I would comment that the assumption of all the build stuff is that you
are a *nix expert,
who understands the internal working of all these utilities. They are fine
when they work,
but when they go wrong they leave you floundering in deep water.

None of these document what they are going to (try to) do.

Rarely is there any guidance for how to verify they have done what is
expected.

For two simple examples on this particular matter:

1 A few more explanatory words instead of "=DIR" in the instructions, for
example, even a suggestion for where?

2 A verification suggestion like

C:\Users\Paul>bjam --version

Spare more thought for the poor neuronically challenged Microsofties.

Assumption is the mother of all foulups!

Paul

PS Oh - and Norton thinks "bjam.exe" is the Mother of All High Risks, with
only 5 users, and promptly deleted it! ;-)