Re: [bbv2] error invoking bjam for cross-compiler

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2005-10-13 08:04:26

"BRIDGES Dick" wrote
> I compiled bjam from the boost_1_33_0 source, copied user-config.jam to
> the $BOOST_BUILD_PATH and made the following modification:
>
> <user-config.jam mod>
> # Configure gcc (default version)
> using gcc : 3.4 : gcc-3.4 ;
> using gcc : 3.3arm :
> /opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2/bin/arm-sof
> tfloat-linux-gnu-c++ : \
> <cxxflags>-pthread \
> ;
> </user-config.jam mod>
>
> Invoking bjam from $BOOST_BUILD_PATH with:
> # bjam --v2 gcc-3.3arm
> yielded the following error message.
>
> <error-text>
> Building Boost.Regex with the optional Unicode/ICU support disabled.
> Please refer to the Boost.Regex documentation for more information
> (and if you don't know what ICU is then you probably don't need it).

This is a warning because of GCC issues with the Unicode/wide character
libraries.

> warning: Python location is not configured
> warning: the Boost.Python library won't be built

Here is another warning because you don't have Python installed/configured.

> error: "3.3arm" is not a known subfeature value of <toolset>gcc

This is the actual error. The problem is that BBv2 is checking for n.n style
version where n is a number, so it is producing an error on the "arm" bit.
The latest CVS version has support for specifying an <architecture> feature,
so you would need to do:

using gcc : 3.3
:

/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2/bin/arm-sof
tfloat-linux-gnu-c++
:
<cxxflags>-pthread
<architecture>arm
;

However...

1. arm is not a supported value of <architecture>, so you would need to add
it to builtin.jam. NOTE: I am working on support for arm, sh, cex86 and mips
cross-compilers on msvc, so arm will most likely be supported in the future.

2. The <architecture> setting will most likely not be enough if you have
several gcc-3.3 configurations.

You could try:

using gcc : 3.3-arm : ... ;

If that doesn't work, I will look into it next week when I am at my
development machine.

HTH,
- Reece