[Boost-users] problems building Boost-1.55.0 in 32b machines with c++11

Subject: [Boost-users] problems building Boost-1.55.0 in 32b machines with c++11
From: Patricia Mendez Lorenzo (Patricia.Mendez_at_[hidden])
Date: 2015-01-20 04:41:44

Dear Boost experts,

since a while I am trying to compile Boost from the source  in a 32b linux machine with c++11 enabled. The compiler version used is gcc4.8.1

This is performed through cmake as follows:

--> Configuration: bootstrap.sh --with-python=<path to /bin/python> --with-toolset=gcc
--> Build:  /b2 -j4 variant=release --layout=versioned  --debug-configuration --toolset=gcc --user-config=<path to a user-config.jam>

Where user-config.jam contains the following information:
using gcc : : :  <linkflags>-m32 <compileflags>-m32 -std=gnu++0x

also tested it with -std=c++11

And finally installed which basically contains the same options as the build adding --prefix=<installation dir>

The libraries built following this procedure does not seem to have been created with c++11. If I compare the signatures of the same library build in 64 against 32 the result are

In 64:
nm --defined-only --demangle libboost_filesystem-gcc48-mt-1_55.so | grep copy_file

boost::filesystem::detail::copy_file(boost::filesystem::path const&,
boost::filesystem::path const&, boost::filesystem::copy_option, boost::system::error_code*)

In 32, the same produces:

boost::filesystem::detail::copy_file(boost::filesystem::path
const&, boost::filesystem::path const&, boost::filesystem::copy_option::enum_type, boost::system::error_code*)

The difference seems to come from wrong i686 build options. Could you please help me to find the good options to build these libs in 32b with c+=11 enabled?

Thank you so much,