Excerpts from the build log below, and build.log file attached.
Feel free to e-mail me directly so I don’t keep spam’ing everyone. I’d be glad try any build modification for you.
...found 13 targets...
...updating 10 targets...
common.mkdir D:\boostBuild_QCC_1_51_0
common.mkdir D:\boostBuild_QCC_1_51_0\boost
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config\qcc
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config\qcc\debug
common.mkdir D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config\qcc\debug\target-os-qnxnto
qcc.compile.c++ D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config\qcc\debug\target-os-qnxnto\32.o
...updated 10 targets...
Performing configuration checks
- 32-bit : yes
...found 3 targets...
...updating 1 target...
qcc.compile.c++ D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\context\config\qcc\debug\target-os-qnxnto\x86.o
...updated 1 target...
- x86 : yes
error: No best alternative for libs/context/build/asm_context_sources
[trying next alternatives removed]
error: No best alternative for libs/context/build/asm_context_sources
[more - trying next alternatives removed]
next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>gcc
not matched
...found 13 targets...
...updating 7 targets...
[lots of noise about icu related to boost::locale]
...updated 6 targets...
- gcc visibility : yes
...found 47 targets...
...updating 1 target...
qcc.compile.c++ D:\boostBuild_QCC_1_51_0\boost\bin.v2\libs\math\config\qcc\debug\target-os-qnxnto\has_long_double_support.o
...updated 1 target...
- long double support : yes
error: No best alternative for libs/context/build/asm_context_sources
next alternative: required properties: <abi>aapcs <architecture>arm <binary-format>elf <toolset>gcc
[ more alternative trying ]
not matched
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
Component configuration:
- chrono : building
- context : building
- date_time : building
- exception : building
- filesystem : building
- graph : building
- graph_parallel : building
- iostreams : building
- locale : building
- math : building
- mpi : not building
- program_options : building
- python : not building
- random : building
- regex : building
- serialization : building
- signals : building
- system : building
- test : building
- thread : building
- timer : building
- wave : building
SGL
From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Oliver Kowalke
Sent: Wednesday, August 22, 2012 10:51 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] 1.51 build issue, I think...
Am 22.08.2012 19:43, schrieb Lemay.Steve:
The qcc toolset basically “wraps” the gcc environment. The current supported compiler is gcc 4.4.2. I believe QNX provides free downloads of the development environment, as well as a pre-made QNX hosted VM. The 30 day trial license can be found here: http://www.qnx.com/products/evaluation/ I get the same issue with qcc 4.7.1 (which is currently considered prototype).
I seemed to get the same result with this change. (but, I don’t really know specifically what I’m doing in bjam files)
if ( ! ( <toolset>gcc in $(properties)
|| <toolset>qcc in $(properties)
|| <toolset>intel in $(properties)
|| <toolset>msvc in $(properties) ) )
you don't see stuff like
Performing configuration checks
- 32-bit : no
- 64-bit : yes
- x86 : yes
...patience...
...found 1002 targets...
...updating 20 targets...
gcc.compile.c++ ../../../bin.v2/libs/test/build/gcc-4.6/debug/link-static/unit_test_main.o
...
?
Oliver
From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Oliver Kowalke
Sent: Wednesday, August 22, 2012 10:18 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] 1.51 build issue, I think...
Am 22.08.2012 17:47, schrieb Lemay.Steve:
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) ;
}
I don't know qcc, but if I look inside tools/build/v2/tools/qcc.jam it is derived from gcc.
The question is if you could use gcc as toolset value on QNX too (bjam toolset=gcc)?
Is GNU as available and installed on QNX (required to compile the assembler)?
Maybe you could try to add <toolset>qcc in $(properties) in rule configure.
Is a free version of QNX available? AFAIK some years ago it was but the new owner of QNX has revoked the free license.
Oliver
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users