Re: [boost] [Boost-users] [1.55.0] Release candidate 2 available

Subject: Re: [boost] [Boost-users] [1.55.0] Release candidate 2 available
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-11-05 06:50:05

On Tue, Nov 5, 2013 at 3:45 PM, Frédéric Bron <frederic.bron_at_[hidden]> wrote:
> Hi,
>
> When I build the library (1.55.0 rc2) on x86_64 linux using a gcc
> cross-compiler to target i686-w64-mingw32 or x86_64-w64-mingw32, I get
> this error in the 'log' library:
>
> gcc.compile.c++
> bin.v2/libs/log/build/gcc-mingw-4.8.2/release/address-model-32/link-static/log-api-winnt/target-os-windows/threadapi-win32/threading-multi/event_log_backend.o
>
>     "i686-w64-mingw32-g++-4.8.2"  -ftemplate-depth-128 -O3
> -finline-functions -Wno-inline -Wall -mthreads -m32
> -fno-strict-aliasing -ftemplate-depth-1024 -DBOOST_ALL_NO_LIB=1
> -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_FILESYSTEM_STATIC_LINK=1
> -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_USE_AVX2
> -DBOOST_LOG_USE_SSSE3 -DBOOST_SPIRIT_USE_PHOENIX_V3=1
> -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1
> -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_DONT_USE_CHRONO=1
> -DBOOST_THREAD_USE_LIB=1 -DDATE_TIME_INLINE -DNDEBUG  -I"."
> -I"bin.v2/libs/log/build/gcc-mingw-4.8.2/release/address-model-32/link-static/log-api-winnt/target-os-windows/threadapi-win32/threading-multi"
> -c -o "bin.v2/libs/log/build/gcc-mingw-4.8.2/release/address-model-32/link-static/log-api-winnt/target-os-windows/threadapi-win32/threading-multi/event_log_backend.o"
> "libs/log/src/event_log_backend.cpp"
>
> libs/log/src/event_log_backend.cpp:36:30: fatal error:
> simple_event_log.h: No such file or directory
>  #include "simple_event_log.h"
>                               ^
> compilation terminated.
> ...failed gcc.compile.c++
> bin.v2/libs/log/build/gcc-mingw-4.8.2/release/address-model-32/link-static/log-api-winnt/target-os-windows/threadapi-win32/threading-multi/event_log_backend.o...
>
> Here are my commands:
> $ CC="i686-w64-mingw32-gcc-4.8.2" CFLAGS="-O2 -DNDEBUG -ffloat-store"
> CXX="i686-w64-mingw32-g++-4.8.2" CXXFLAGS="-O2 -DNDEBUG -ffloat-store
> -std=c++98 -DBOOST_THREAD_USE_LIB" AR="i686-w64-mingw32-ar"
> AS="i686-w64-mingw32-as" RANLIB="i686-w64-mingw32-ranlib"
> ./bootstrap.sh --without-icu
> --prefix=/cm/shared/apps/soft/bal/usr/mingw32-4.8.2-c++98-release/boost
> --with-toolset=gcc
> $ ./b2 -d2 -j16
> -sBZIP2_INCLUDE=/path/to/mingw32-4.8.2-c++98-release/bzip2/include
> -sBZIP2_LIBPATH=/path/to/mingw32-4.8.2-c++98-release/bzip2/lib
> -sZLIB_INCLUDE=/path/to/mingw32-4.8.2-c++98-release/zlib/include
> -sZLIB_LIBPATH=/path/to/mingw32-4.8.2-c++98-release/zlib/lib
> --layout=system --user-config=user-config.jam --without-mpi
> --without-python --without-context --without-coroutine link=static
> threading=multi runtime-link=shared target-os=windows threadapi=win32
> address-model=32 variant=release install

Do you have message compiler (mc.exe) installed? Is it found by bjam
(see the beginning of the build log)? Are there errors when compiling
the mc file in the build log?