Shit. Looks like I broke something
When I run the status tests; I get the following error [ Revision 77175; gcc 4.2.1; Mac OS X 10.7.3; toolset darwin ]
cd $BOOST/trunk/status ../b2 MPI auto-detection failed: unknown wrapper compiler mpic++ Please report this error to the Boost mailing list: http://www.boost.org You will need to manually configure MPI support. Performing configuration checks
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build <toolset>darwin /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:482: in build-main-targets from module object(project-target)@192 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:332: in main-target from module object(project-target)@192 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:397: in find-really from module object(project-target)@192 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:435: in object(project-target)@192.find from module object(project-target)@192 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:373: in find-really from module object(project-target)@2522 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:435: in object(project-target)@2522.find from module object(project-target)@2522 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:816: in resolve-reference from module targets /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:833: in targets.generate-from-reference from module targets /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:1217: in generate-dependencies from module object(alias-target-class)@2529 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:1266: in object(alias-target-class)@2529.generate from module object(alias-target-class)@2529 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:732: in generate-really from module object(main-target)@26276 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:704: in object(main-target)@26276.generate from module object(main-target)@26276 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:258: in object(project-target)@2522.generate from module object(project-target)@2522 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:258: in object(project-target)@827.generate from module object(project-target)@827 /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build-system.jam:736: in load from module build-system /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/kernel/modules.jam:283: in import from module modules /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /Volumes/EyeFive/Marshall/Sources/boost/trunk/boost-build.jam:17: in module scope from module
I was building fine; I checked in r77115, which was a bunch of changes in libs/config/test; ran the tests there, all was well. Then I tried a full regression test, and got this. Maybe it was the other changes that were made to build (77190/91/92/93), but they look benign to me. Suggestions on the best way to debug this? -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
On Mar 3, 2012, at 7:47 PM, Marshall Clow wrote:
When I run the status tests; I get the following error [ Revision 77175; gcc 4.2.1; Mac OS X 10.7.3; toolset darwin ]
cd $BOOST/trunk/status ../b2 MPI auto-detection failed: unknown wrapper compiler mpic++ Please report this error to the Boost mailing list: http://www.boost.org You will need to manually configure MPI support. Performing configuration checks
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build <toolset>darwin
Ok - It wasn't my latest changes. Building from 77193 gives the same results
Maybe it was the other changes that were made to build (77190/91/92/93), but they look benign to me. Suggestions on the best way to debug this?
-- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
AMDG On 03/03/2012 08:09 PM, Marshall Clow wrote:
On Mar 3, 2012, at 7:47 PM, Marshall Clow wrote:
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build <toolset>darwin
Ok - It wasn't my latest changes. Building from 77193 gives the same results
It was introduced in r77191 and should be fixed in r77196. Basically, the message target is buggy and can't safely be used as a target alternative.
Maybe it was the other changes that were made to build (77190/91/92/93), but they look benign to me. Suggestions on the best way to debug this?
In Christ, Steven Watanabe
On Mar 3, 2012, at 8:21 PM, Steven Watanabe wrote:
AMDG
On 03/03/2012 08:09 PM, Marshall Clow wrote:
On Mar 3, 2012, at 7:47 PM, Marshall Clow wrote:
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build <toolset>darwin
Ok - It wasn't my latest changes. Building from 77193 gives the same results
It was introduced in r77191 and should be fixed in r77196. Basically, the message target is buggy and can't safely be used as a target alternative.
Maybe it was the other changes that were made to build (77190/91/92/93), but they look benign to me. Suggestions on the best way to debug this?
Thanks, Steven. Updating to r77196 solved the problem. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
Am 04.03.2012 05:35, schrieb Marshall Clow:
On Mar 3, 2012, at 8:21 PM, Steven Watanabe wrote:
AMDG
On 03/03/2012 08:09 PM, Marshall Clow wrote:
On Mar 3, 2012, at 7:47 PM, Marshall Clow wrote:
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build<toolset>darwin Ok - It wasn't my latest changes. Building from 77193 gives the same results
It was introduced in r77191 and should be fixed in r77196. Basically, the message target is buggy and can't safely be used as a target alternative.
Maybe it was the other changes that were made to build (77190/91/92/93), but they look benign to me. Suggestions on the best way to debug this? Thanks, Steven.
Updating to r77196 solved the problem.
-- Marshall
Marshall Clow Idio Software<mailto:mclow.lists@gmail.com>
A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
_______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
on x86-64 I get an error that the cpu does not support the instruction-set. -d2 option shows: -march=i386 -m64 Oliver
Am 04.03.2012 16:11, schrieb Steven Watanabe:
AMDG
On 03/04/2012 12:50 AM, Oliver Kowalke wrote:
on x86-64 I get an error that the cpu does not support the instruction-set. -d2 option shows: -march=i386 -m64
Fixed in r77218.
r77218 reverted 77216 which was intended to fix the arm -m32 bug for gcc. I fixed problem with gcc options -march=i386 -m64 in 77201 (remove default 'i386) for x86) - did you notice this? Oliver
AMDG On 03/04/2012 07:51 AM, Oliver Kowalke wrote:
Am 04.03.2012 16:11, schrieb Steven Watanabe:
AMDG
On 03/04/2012 12:50 AM, Oliver Kowalke wrote:
on x86-64 I get an error that the cpu does not support the instruction-set. -d2 option shows: -march=i386 -m64
Fixed in r77218.
r77218 reverted 77216 which was intended to fix the arm -m32 bug for gcc.
No. That was r77219.
I fixed problem with gcc options -march=i386 -m64 in 77201 (remove default 'i386) for x86) - did you notice this?
In Christ, Steven Watanabe
Am 04.03.2012 16:11, schrieb Steven Watanabe:
Fixed in r77218.
sorry - r77218 does not fix things - you only removed the test of '<address-model>32' in libs/context/build/Jamfile. I believe this is not the correct way because ARMv8 does support 64bit with its A64 extensions. Without the test in Jamfile I can not select the correct assembler (32bit/64bit version). So I request you the revert it and apply my previous patch again.
AMDG On 03/04/2012 08:22 AM, Oliver Kowalke wrote:
Am 04.03.2012 16:11, schrieb Steven Watanabe:
Fixed in r77218.
sorry - r77218 does not fix things - you only removed the test of '<address-model>32' in libs/context/build/Jamfile.
Huh? r77218 didn't remove anything. I just shuffled the aliases around so the deduced architecture and address-model only affected selecting the correct alternative, not the build commands.
I believe this is not the correct way because ARMv8 does support 64bit with its A64 extensions. Without the test in Jamfile I can not select the correct assembler (32bit/64bit version). So I request you the revert it and apply my previous patch again.
In Christ, Steven Watanabe
Am 04.03.2012 20:37, schrieb Steven Watanabe:
AMDG
Am 04.03.2012 16:11, schrieb Steven Watanabe:
Fixed in r77218. sorry - r77218 does not fix things - you only removed the test of '<address-model>32' in libs/context/build/Jamfile. Huh? r77218 didn't remove anything. I just shuffled the aliases around so the deduced architecture and address-model only affected selecting the correct alternative, not
On 03/04/2012 08:22 AM, Oliver Kowalke wrote: the build commands.
Hmm - I thought I was testing for the architecture and address-model in the Jamfile and was wondering that it seamed to be vanished?! Anyway - ARM has published its new 64bit ARMv8 architecture last year - I believe gcc-4.7 supports the new instruction-set. Would it be easy to prepare boost.build for it? Oliver
AMDG On 03/04/2012 11:45 AM, Oliver Kowalke wrote:
Anyway - ARM has published its new 64bit ARMv8 architecture last year - I believe gcc-4.7 supports the new instruction-set.
Would it be easy to prepare boost.build for it?
It shouldn't be too hard. What options need to be passed to gcc? In Christ, Steven Watanabe
AMDG On 03/03/2012 07:47 PM, Marshall Clow wrote:
When I run the status tests; I get the following error [ Revision 77175; gcc 4.2.1; Mac OS X 10.7.3; toolset darwin ]
cd $BOOST/trunk/status ../b2 MPI auto-detection failed: unknown wrapper compiler mpic++ Please report this error to the Boost mailing list: http://www.boost.org You will need to manually configure MPI support. Performing configuration checks
- has_icu builds : no /Volumes/EyeFive/Marshall/Sources/boost/trunk/tools/build/v2/build/targets.jam:604: in object(main-target)@26280.add-alternative from module object(main-target)@26280 error: default build must be identical in all alternatives error: main target is ../libs/context/build/asm_context_sources error: with error: differing from previous default build <toolset>darwin
This looks like my fault. (r77191/r77196) In Christ, Steven Watanabe
participants (3)
-
Marshall Clow -
Oliver Kowalke -
Steven Watanabe