Re: [Boost-build] GNU Cross Compiler Support?

From: Norbert Unterberg (nunterberg_at_[hidden])
Date: 2007-01-19 07:50:20

Volodya,

Vladimir Prus schrieb:
> On Monday 15 January 2007 19:18, Norbert Unterberg wrote:
> 
>>We are running a cross compiler toolchain under Cygwin/Windows. This
>>toolchain uses a cuistomized gcc compiler to generate code for a linux
>>target.
>>
> 
> Do you mean the extension is wrong, or that the build process is wrong?
> I've looked at the code in question and there are very few platform-specific
> differences.

The build does not succeed.

I have downloaded and extracted boost, so I have a boost_1_33_1 folder. 
I then downloaded boost-jam-3.1.13-1-ntx86 and copied the bjam.exe into 
this folder.

I then try to build Boost.Threads (as an example) from within a cygwin 
command shell, using the command line:

./bjam -sTOOLS=gcc 
-sGCC_ROOT_DIRECTORY=/opt/elinos-4.1/cdk/x86/486/glibc-2.3.4 
-sGXX=x86_486-g++ -sGCC=x86_486-gcc --with-thread stage

as described by http://www.boost.org/more/getting_started.html

This is what I get:

******************************************************
Building Boost.Iostreams with bzip2 support disabled.
To enable bzip2, consult the Boost.Iostreams documentation
******************************************************
******************************************************
Building Boost.Iostreams with zlib and gzip support disabled.
To enable zlib and gzip, consult the Boost.Iostreams documentation
******************************************************
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).
...found 382 targets...
...updating 93 targets...
gcc-C++-action 
bin\boost\libs\thread\build\boost_thread.dll\gcc\debug\threading-multi\exceptions.obj
Das System kann den angegebenen Pfad nicht finden.
(--> translated: can not find the specified path)

     "/opt/elinos-4.1/cdk/x86/486/glibc-2.3.4\bin\x86_486-g++"  -c -Wall 
-ftemplate-depth-255  -DBOOST_THREAD_LIB_NAME=boost_thread -DBOOST_THREAD_BU
ILD_DLL=1 -g -O0 -fno-inline -mthreads  -I"bin\boost\libs\thread\build" 
  -I "d:\boost\boost_1_33_1" -o 
"bin\boost\libs\thread\build\boost_thread.dll
\gcc\debug\threading-multi\exceptions.obj" 
"d:\boost\boost_1_33_1\libs\thread\build\..\src\exceptions.cpp"

...failed gcc-C++-action 
bin\boost\libs\thread\build\boost_thread.dll\gcc\debug\threading-multi\exceptions.obj...
gcc-C++-action 
bin\boost\libs\thread\build\boost_thread.dll\gcc\debug\threading-multi\mutex.obj
Das System kann den angegebenen Pfad nicht finden.
(--> translated: can not find the specified path)

... and so on, until finally ...

...skipped 
<@boost!libs!thread!build\libboost_thread.lib\gcc\release\threading-multi>libboost_thread-gcc-mt-1_33_1.lib 
for lack of 
<@boost!libs!thread!build\libboost_thread.lib\gcc\release\threading-multi>barrier.obj...
...skipped <@boost!lib>libboost_thread-gcc-mt-1_33_1.lib for lack of 
<@boost!libs!thread!build\libboost_thread.lib\gcc\release\threading-multi>libboost_thread-gcc-mt-1_33_1.lib...
...skipped <@boost!lib>boost_thread-gcc-mt-d.lib for lack of 
<@boost!lib>boost_thread-gcc-mt-d-1_33_1.lib...
...skipped <@boost!lib>boost_thread-gcc-mt.lib for lack of 
<@boost!lib>boost_thread-gcc-mt-1_33_1.lib...
...skipped <@boost!lib>libboost_thread-gcc-mt-sd.lib for lack of 
<@boost!lib>libboost_thread-gcc-mt-sd-1_33_1.lib...
...skipped <@boost!lib>libboost_thread-gcc-mt-d.lib for lack of 
<@boost!lib>libboost_thread-gcc-mt-d-1_33_1.lib...
...skipped <@boost!lib>libboost_thread-gcc-mt-s.lib for lack of 
<@boost!lib>libboost_thread-gcc-mt-s-1_33_1.lib...
...skipped <@boost!lib>libboost_thread-gcc-mt.lib for lack of 
<@boost!lib>libboost_thread-gcc-mt-1_33_1.lib...
...failed updating 70 targets...
...skipped 22 targets...
...updated 2 targets...

I have no idea where to start, since I do not know jam/bjam.

After the failed build process, the folder
bin\boost\libs\thread\build\boost_thread.dll\gcc\debug\threading-multi
actually exists, but it contains only barrier.obj and condition.obj, but 
no exceptions.obj (which was named in the error message above).

Any help is appreciated.

Norbert Unterberg