[haiku-commits] Re: BOM: r35473 ...failed BuildHaikuImage1 generated/haiku.vmdk ...
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Mon, 15 Feb 2010 20:05:52 +0000
On Mon, Feb 15, 2010 at 19:07, <buildomatic@xxxxxxxxx> wrote:
> Host OS : FreeBSD 8.0-RELEASE-p2 i386 32bit
> Affected Targets:
>
> x86gcc2 : ../haiku/configure --use-gcc-pipe --use-xattr
> --cross-tools-prefix
> /Build-O-Matic/rewrite2/output/generated.x86gcc2/cross-tools/bin/i586-pc-haiku-
> |
> |-- haiku-vmware-image
> | |-- command: jam -q -j1 -sHAIKU_IGNORE_USER_BUILD_CONFIG=1
> haiku-vmware-image
> | |-- last working revision: 35402
> | .
> |
> .
>
> x86gcc4 : ../haiku/configure --use-gcc-pipe --use-xattr
> --cross-tools-prefix
> /Build-O-Matic/rewrite2/output/generated.x86gcc4/cross-tools/bin/i586-pc-haiku-
> |
> |-- haiku-vmware-image
> | |-- command: jam -q -j1 -sHAIKU_IGNORE_USER_BUILD_CONFIG=1
> haiku-vmware-image
> | |-- last working revision: 35402
> | .
> |
> .
>
> Log Snippet :
>
Sorry about the flurry of emails for r35473. My error abstraction
methods are a constant work in progress.
Soon, i'll be adding logic to abstract jam targets (@alpha-raw,
haiku-cd, ...) as "<jamtarget>" and their respective output files
(haiku.vmdk, haiku.image, ...) as "<jamtarget-outputfile>"
--mmadia
Other related posts:
