Re: [Boost-users] 1.51 build issue, I think...

22 Aug 2012

      do you use the bjam version provided by boost-1.51?
Yes, bjam is created on the first build.  I'm using QNX SDK 6.5 SP1 on a Windows hosted development environment.  VS2012 also installed.  Contents of batch file provide below. (gcc 4.4.2 support, and gcc 4.7.1 prototype)

on which architecture you have QNX running (i386/x8664,arm, mips, ...), which binary format and which ABI is used?

Although the SDK support several target processors, this builds target for x86 (AMD K8 architecture - 32-bit addressing). I believe ELF and SYSV (still need to verify) and the boost toolset configuration is set to qcc (not gcc).  Is there a good/simple way to verify the ABI?

As I am not very familiar with bjam syntax - could the boost_1_51_0\libs\context\build\jamfile.v2 just be confused because of the toolset definition?  Considering qcc wraps gcc...?  I'm looking specifically at:

rule configure ( properties * )
{
    local result  ;

    if ( ! ( <toolset>gcc in $(properties)
            || <toolset>intel in $(properties)
            || <toolset>msvc in $(properties) ) )
    {
        result = <build>no ;
        ECHO "toolset not supported" ;
    }

    return $(result) ;
}

================= Example of building boost for use with QNX 6.5 SDK ==================

@ECHO OFF
:: In file tools\build\v2\tools\qcc.jam, in the "actions piecemeal archive" block, replace the line: ar rc "$(<)" "$(>)" with the following: ntox86-ar rc "$(<)" "$(>)"
:: For Boost 1.50 modify the following files until the bug is addressed.
::   boost\serialization\factory.hpp - line 27 remove "|| defined (__QNXNTO__)"
::   boost\test\impl\execution_monitor.ipp - add to line 56 "|| defined (__QNXNTO__)" remove line 61-66 as no longer necessary.

CLS
SET DRIVE=D:
SET BOOSTVER=1_51_0

@PUSHD %DRIVE%\boost_%BOOSTVER%

@IF NOT EXIST bjam.exe call bootstrap
@IF NOT EXIST bjam.txt bjam --help > bjam.txt
@IF NOT EXIST bjam_libs.txt bjam --show-libraries > bjam_libs.txt
@IF NOT EXIST bjam_obscure_options.txt bjam --help-options > bjam_obscure_options.txt
@IF EXIST build.log del build.log

@ECHO ON
@ECHO Building Boost libraries for QNX 6.5.x

@REM Static library
@REM bjam -a -q -j4 --prefix=%DRIVE%\boost --build-type=minimal --build-dir=%DRIVE%\boostBuild_QCC_%BOOSTVER% --layout=system toolset=qcc target-os=qnxnto threadapi=pthread --variant=release link=static threading=multi runtime-link=shared cxxflags="-DFD_SETSIZE=2048 -march=k8-sse3 -mtune=k8-sse3 -mmmx -msse3 -mfpmath=sse -mno-3dnow -mstackrealign -Wc,-fPIC,-fnothrow-opt,-std=c++11,-std=gnu++11" --without-mpi --without-python install >build.log 2>&1
bjam -a -q -j4 --prefix=%DRIVE%\boost --build-type=minimal --build-dir=%DRIVE%\boostBuild_QCC_%BOOSTVER% --layout=system toolset=qcc target-os=qnxnto threadapi=pthread --variant=release link=static threading=multi runtime-link=shared cxxflags="-DFD_SETSIZE=2048 -march=k8-sse3 -mtune=k8-sse3 -mmmx -msse3 -mfpmath=sse -mno-3dnow -mstackrealign -Wc,-fPIC,-std=c++0x,-std=gnu++0x" --without-mpi --without-python install >build.log 2>&1

@POPD

SGL
steven.lemay@igt.commailto:steven.lemay@igt.com

From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Oliver Kowalke
Sent: Tuesday, August 21, 2012 9:27 PM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] 1.51 build issue, I think...

do you use the bjam version provided by boost-1.51?
on which architecture you have QNX running (i386/x8664,arm, mips, ...), which binary format and wich ABI is used.
otherwise QNX is not supported by boost.context.

Oliver

Am 22.08.2012 00:32, schrieb Lemay.Steve:
I am new to building boost, so I apologize if this is an uninformed question.  I was able to build the boost 1.49 and 1.50 libraries using qcc 4.4.2 (QNX's gcc 4.4.2) without major issues.  Boost 1.51 has added a new wrinkle, and I'm not sure how to address it.  Here's a snipit from the build.log.  Any help is appreciated.

error: No best alternative for libs/context/build/asm_context_sources
    next alternative: required properties: <abi>aapcs <architecture>arm <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>aapcs <architecture>arm <binary-format>elf
        not matched
    next alternative: required properties: <abi>o32 <architecture>mips1 <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>o32 <architecture>mips1 <binary-format>elf
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <toolset>intel
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>intel
        not matched
    next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin
        not matched
    next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>intel
        not matched
    next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>msvc
        not matched
    next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <toolset>intel
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>gcc
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>intel
        not matched
    next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin
        not matched
    next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>intel
        not matched
    next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>msvc
        not matched
    next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>gcc
        not matched

_______________________________________________

Boost-users mailing list

Boost-users@lists.boost.orgmailto:Boost-users@lists.boost.org

http://lists.boost.org/mailman/listinfo.cgi/boost-users