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

Subject: Re: [boost] [Boost-users] [1.55.0] Release candidate 2 available
From: Frédéric Bron (frederic.bron_at_[hidden])
Date: 2013-11-05 06:58:10

>> 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:
>>
>> libs/log/src/event_log_backend.cpp:36:30: fatal error:
>> simple_event_log.h: No such file or directory
>
> 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?

good point: it tries to call mc but that calls midnight commander on
linux (see below). What should I do?

Frédéric

mc.compile 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/simple_event_log.h

    mc  -h "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"
-r "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"
"libs/log/src/simple_event_log.mc"

Usage:
  mc [OPTION...] [+number] [this_dir] [other_panel_dir]
 +number - Set initial line number for the internal editor

GNU Midnight Commander 4.7.0.2

Help Options:
  -h, --help                     Show help options
  --help-all                     Show all help options
  --help-terminal                Terminal options
  --help-color                   Color options
...

compile.resource.null
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/simple_event_log_res.o

    as /dev/null -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/simple_event_log_res.o"