Hi Nikola,
There is a spec file in dist/lfs-5.1/boost/ (you probably found that) which may be a useful starting point. However, it was inherited from an old project I did and has never been properly ported to the LTIB environment.
Unfortunately I've not worked on this package for a long time and I'm also tied up at the moment and so don't have time right now to look into it.
Regards, Stuart
On Thu, 2008-05-29 at 22:21 -0700, Nikola Trajic wrote:
Hi,
a) Could someone please confirm BJAM is tools/build/jam_src/bin.linuxx86/bjam when cross-compiling?
b) What is the proper BJAM command line?
c) What additional configurations (of compiler in bjam build env., etc) are necessary?
Thanks,
Nik
DETAILS:
I tried configuring C1 and C2, in vain.
C1)
/boost_1_31_0/tools/build/v2/user-config.jam
…
# Configure specific gcc version, giving alternative name to use
# using gcc : 3.2 g++-3.2 ;
using gcc: 4.1.2 arm-none-linux-gnueabi-g++ ;
…
C2)
In the /opt/bsp/ltib/BUILD/boost_1_31_0/ :
export GCC_PREFIX=arm-linux-
I tried modifying /opt/bsp/ltib/BUILD/boost_1_31_0/tools/build/v1/gcc-tools.jam
by putting this prefix in gcc-tools.jam
then update:
flags gcc .GXX : $GCC_PREFIX)$(GXX)
flags gcc .GCC : $(GCC_PREFIX)$(GCC)
flags gcc .OBJCOPY : [ GLOB $(GCC_BIN_DIRECTORY) $(PATH) : $(GCC_PREFIX)objcopy ] ;
flags gcc .AR : [ GLOB $(GCC_BIN_DIRECTORY) $(PATH) : $(GCC_PREFIX) ar ar.exe ] ;
I tried the following bjam command lines:
Pre-requisite:
cd tools/build/jam_src && sudo ./build.sh
BJAM=`find tools/build/jam_src/ -name bjam -a -type f`
B1) $BJAM -sTOOLS=gcc -sGCC_PREFIX=arm-linux- stage // for C2)
--------
B)
export PYTHON_ROOT=/usr/local/bin
export PYTHON_VERSION=2.4
export PYTHON_LIB_PATH=/usr/local/lib/python2.4/config
export PYTHON_INCLUDES=/usr/local/include/python2.4
export GCC_ROOT_DIRECTORY=/opt/freescale/toolchain
export GCC=arm-none-linux-gnueabi-gcc
export GXX=arm-none-linux-gnueabi-g++
address@hidden:/opt/bsp/ltib/BUILD/boost_1_31_0$ echo $BJAM
tools/build/jam_src/bin.linuxx86/bjam
$BJAM "$PYTHON_FLAGS" "-sGCC_ROOT_DIRECTORY=$GCC_ROOT_DIRECTORY" "-sGCC=$GCC" "-sGXX=$GXX" stage > arm.log 2>&1 &
arm.log snippet:
-----
set -e
/opt/freescale/toolchain/bin//arm-none-linux-gnueabi-g++ -c -Wall -ftemplate-depth-100 -DBOOST_PYTHON_DYNAMIC_LIB -DBOOST_PYTHON_SOURCE -g -O0 -fno-inline -pthread -fPIC -I"bin/boost/libs/python/build" -I "/usr/local/include/python2.4" -I "/opt/bsp/ltib-imx27ads-20071219/rpm/BUILD/boost_1_31_0" -o "bin/boost/libs/python/build/libboost_python.so/gcc/debug/shared-linkable-true/threading-multi/list.o" "/opt/bsp/ltib-imx27ads-20071219/rpm/BUILD/boost_1_31_0/libs/python/build/../src/list.cpp"
/usr/bin/objcopy --set-section-flags .debug_str=contents,debug "bin/boost/libs/python/build/libboost_python.so/gcc/debug/shared-linkable-true/threading-multi/list.o"
...failed gcc-C++-action bin/boost/libs/python/build/libboost_python.so/gcc/debug/shared-linkable-true/threading-multi/list.o...
...removingbin/boost/libs/python/build/libboost_python.so/gcc/debug/shared-linkable-true/threading-multi/list.o
/opt/bsp/ltib-imx27ads-20071219/rpm/BUILD/boost_1_31_0/boost/config/compiler/gcc.hpp:92:7: warning: #warning "Unknown compiler version - please run the configure tests and report the results"
-----
From: Nikola Trajic
Sent: Thursday, May 29, 2008 4:24 PM
To: 'address@hidden'
Cc: 'address@hidden'
Subject: boost thread lib cross-compiled for arm
Hi,
I am trying to cross-compile the boost thread lib for arm926 (i.mx27).
I have successfully cross compiled Python 2.4.
It is easy to build boost suite of libs for x86.
Could you please provide a pointer how BJAM compiler is supposed to pick the arch-arm architecture in a non-standard way (without configure)?
Do you have a working LTIB spec, or please describe how this should be built in a few words?
Thanks,
Nik.
|