|
|
Boost Testing : |
Subject: Re: [Boost-testing] Trunk nightly target alternative failures
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-05-31 14:06:07
AMDG
On 05/31/2012 09:48 AM, Belcourt, Kenneth wrote:
> Hi,
>
> I don't know when this showed up but trunk nightly testing now has boatloads of diagnostics like this, could someone please fix this up?
>
a) What toolset?
b) What's in config.log?
> -- Noel
>
> Performing configuration checks
>
> - has_icu builds : no
> - 32-bit : no
> - 64-bit : no
> - x86 : no
> - power : no
> - arm : no
> - mips1 : no
> 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
>
In Christ,
Steven Watanabe