This is how I'm compiling boost:

sudo bjam install --prefix=/usr/local/boost_1_42_0 --layout=system -toolset=gcc-arm link=static runtime-link=static

I still need the arquitecture=arm?

-----||-----
project-config.jam
# Boost.Build Configuration
# Automatically generated by bootstrap.sh

import option ;
import feature ;

# Compiler configuration. This definition will be used unless
# you already have defined some toolsets in your user-config.jam
# file.
if ! gcc in [ feature.values <toolset> ]
{
    using gcc : arm : /home/carlos/arm/arm-2009q3/bin/arm-none-linux-gnueabi-g++  ;
}

project : default-build <toolset>gcc ;

# Python configuration
using python : 2.6 : /usr ;

path-constant ICU_PATH : /usr ;


# List of --with-<library> and --without-<library>
# options. If left empty, all libraries will be built.
# Options specified on the command line completely
# override this variable.
libraries =  ;

# These settings are equivivalent to corresponding command-line
# options.
option.set prefix : /usr/local ;
option.set exec-prefix : /usr/local ;
option.set libdir : /usr/local/lib ;
option.set includedir : /usr/local/include ;


-----||-----

/usr/share/boost-build/user-config.jam
# Copyright 2003, 2005 Douglas Gregor
# Copyright 2004 John Maddock
# Copyright 2002, 2003, 2004 Vladimir Prus
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)

#  This file is used to configure your Boost.Build installation. Please read
#  the user manual to find out where to put it.

#  Toolset declarations are most important in this file. They tell Boost.Build
#  what compilers are available and where to look for them. The first toolset
#  will become "default" one.
#  Some important libraries can also be configured.
#  Uncomment relevant parts to suite your local configuration and preferences.

#  GCC configuration

#  Configure gcc (default version)
#  using gcc ;
using gcc : arm : /home/carlos/arm/arm-2009q3/bin/arm-none-linux-gnueabi-g++  ;


#  Configure specific gcc version, giving alternative name to use
#  using gcc : 3.2 : g++-3.2 ;

#  MSVC configuration

#  Configure msvc (default version, searched in standard location
#  and PATH).
#  using msvc ;

#  Borland configuration
#  using borland ;


#  STLPort configuration

#  Configure, specifying location of STLPort headers.
#  Libraries must be either not needed, or available to
#  the compiler by default
#  using stlport : : /usr/include/stlport ;

#  Configure, specifying locatioh of both headers and libraries
#  using stlport : : /usr/include/stlport /usr/lib ;


#  QT configuration

#  Configure, assuming QTDIR gives the installation prefix
#  using qt ;

#  Configure with explicit installation prefix
#  using qt : /usr/opt/qt ;

-----||-----

I've doing some testes and if I compile this way he don't complain:
arm-none-linux-gnueabi-gcc -o main -g -O2  -I/usr/local/boost_1_42_0//include  -L/usr/local/boost_1_42_0//lib main.c /usr/local/boost_1_33_1/lib/libboost_thread-mt.a

but if I use the -lboost_thread flag he give the error I told in the first post:
arm-none-linux-gnueabi-gcc -o main -g -O2  -I/usr/local/boost_1_42_0//include  -L/usr/local/boost_1_42_0//lib main.c -lboost_thread

I try to change the ax_boost_thread.m4 so I could give the correct path but with no sucess.
I'm out of ideias to resolve this.....



On Wed, Feb 24, 2010 at 2:25 PM, Igor R <boost.lists@gmail.com> wrote:
> I'm some weeks trying to resolve a problem in static linking a boost
> library. The compiler finds the library but it says that it is incompatible.

Did you try to add architecture=arm to bjam line?
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users