I had the same problem in the same circumstance. Just hacked mine to call
the correct objcopy.
Did you get the whole boost system to build cleanly - I am still seeing
problems (although a very recent post may have explained why)
James
-----Original Message-----
From: Vladimir Michl [mailto:vladimir.michl@seznam.cz]
Sent: 10 January 2006 17:03
To: boost-users
Subject: [Boost-users] Cross compiling boost libraries with gcc and
using boost jam to crosscompile third-party library (Jambase problem)
Hi all in this list,
recently I was put into task to cross compile boost for ARM platform
with GCC.
My building platform is i386 Linux with gcc and cross compiling to arm
Linux.
Standard way for this kind of compilation is, that name of cross
compiler (running under i386 but producing arm code) and all cross
binary utilities are prefixed by target plarform, so like arm-linux-gcc,
arm-linux-g++, arm-linux-ar, arm-linux-objcopy for arm-linux.
And this is causing a bit of problem with boost.
I can force GCC and GXX, but still have a problem with ar and objcopy.
I've tried to setup GCC_BIN_DIRECTORY but it didn't work.
So I've done a small patch to tools/build/v1/gcc-tools.jam adding
GCC_PREFIX variable, that if set up, will prefix names of all tools with
that prefix.
So I can compile boost with
bjam -sTOOLS=gcc -sGCC_PREFIX=arm-linux- stage
May be it will be useful to add the same functionality to
gcc-stlport-tools.jam or mingw.
So please find attached changes.
It is possible to include them into next boost release?
By the way, the same problem appears when boost jam is used to compile
some third-party libraries. Is this place good to talk about boost jam
and its Jambase file?
Vlad
--
Vladimir Michl