Problems compiling Boost_1_45_0
Hi all, I recently decided to try and compile/install Boost for my MSYS/MinGW64 system. I downloaded the lastest sources for both bjam (3.1.18) and Boost itself (1.45.0). (More precise details of my sytem are below). I compiled my own bjam with no hassle and got a bin.ntx86_64 version and copied it to /mingw/bin. I used the generic command to build it (./build.sh) and let it auto-detect the toolset (gcc). However, the compilation started to fall over once I started to build Boost itself. Using the command /mingw/bin/bjam --prefix=/mingw/boost toolset=gcc address-model=64 variant=release link=shared threading=multi --build-type=complete stage I first received the following error (attachment: error1.txt) After some googling I found a bug report where someone mention the workaround of just removing the 'ignore-minus-q' part of the statement, this removed the errors and allowed me to continue with the build. Is this an acceptable workaround or is there something else that I should be doing here? Anyways, I know receive the following errors (attachment: boost.txt and attachment: boostd2.txt) I did some googling again and found a bug report that is very similar to what I am getting (almost identical except for versions and setup). Here is the link to the bug report https://svn.boost.org/trac/boost/ticket/4839. The attachment boostd2 uses the exact same build command as above but with -d2 tacked on the end. Can anyone tell me why I am getting this and how I might fix it? Regards Bidski System details: OS: Windows 7 Home Premium x64 MinGW64: TDM64-GCC-4.5.1 $ gcc -v Using built-in specs. COLLECT_GCC=c:\mingw\bin\g++.exe COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/x86_64-w64-mingw32/4.5.1/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../../src/gcc-4.5.1/configure --prefix=/crossdev/prefix-tdm64 --build=x86_64-w64-mingw32 --enable-targets=all --enable-libgomp --enable-lto --enable-libstdcxx-debug --enable-languages=c,c++,fortran,objc,obj-c++ --disable-werror --disable-nls --disable-win32-registry --enable-version-specific-runtime-libs --enable-fully-dynamic-string --with-pkgversion=tdm64-1 --with-bugurl=http://tdm-gcc.tdragon.net/bugs Thread model: win32 gcc version 4.5.1 (tdm64-1)
AMDG On 12/30/2010 3:41 PM, Alex Biddulph wrote:
I recently decided to try and compile/install Boost for my MSYS/MinGW64 system. I downloaded the lastest sources for both bjam (3.1.18) and Boost itself (1.45.0). (More precise details of my sytem are below).
I compiled my own bjam with no hassle and got a bin.ntx86_64 version and copied it to /mingw/bin. I used the generic command to build it (./build.sh) and let it auto-detect the toolset (gcc).
However, the compilation started to fall over once I started to build Boost itself. Using the command
/mingw/bin/bjam --prefix=/mingw/boost toolset=gcc address-model=64 variant=release link=shared threading=multi --build-type=complete stage
I first received the following error (attachment: error1.txt)
After some googling I found a bug report where someone mention the workaround of just removing the 'ignore-minus-q' part of the statement, this removed the errors and allowed me to continue with the build. Is this an acceptable workaround or is there something else that I should be doing here?
bjam is included in the Boost distribution (tools/build/v2/engine, I think). use that version. (removing the 'ignore-minus-q' shouldn't cause any problems, unless you use -q, though) In Christ, Steven Watanabe
bjam is included in the Boost distribution (tools/build/v2/engine, I
On 01/01/11 06:27, Steven Watanabe wrote: think).
use that version. (removing the 'ignore-minus-q' shouldn't cause any problems, unless you use -q, though)
Not that it matters, but its in tools/build/v2/engine/src ;) This version of bjam doesn't complain about ignore-minus-q.
This is just a shot in the dark, but does adding define=BOOST_USE_WINDOWS_H to the bjam command line help?
Added this and it compiles nearly perfectly. Just a couple of warnings that look a little suspicious to me. I know that most, if not all, of these are pretty meaningless errors, but I figured that I would mention them anyways. They are in the attachment. Regards Bidski
AMDG On 12/30/2010 3:41 PM, Alex Biddulph wrote:
Anyways, I know receive the following errors (attachment: boost.txt and attachment: boostd2.txt)
I did some googling again and found a bug report that is very similar to what I am getting (almost identical except for versions and setup). Here is the link to the bug report https://svn.boost.org/trac/boost/ticket/4839. The attachment boostd2 uses the exact same build command as above but with -d2 tacked on the end.
Can anyone tell me why I am getting this and how I might fix it?
This is just a shot in the dark, but does adding define=BOOST_USE_WINDOWS_H to the bjam command line help? In Christ, Steven Watanabe
participants (2)
-
Alex Biddulph -
Steven Watanabe