mason.updates was calling download-my-image, which uses the current CPU/OS instead of target-cpu and target-os. So doing 32-bit builds from a 64-bit Factor instance didn't work... oops

db4
Slava Pestov 2008-11-05 05:14:35 -06:00
parent 7f59942219
commit 81c7320f7b
2 changed files with 7 additions and 8 deletions

View File

@ -1,6 +1,6 @@
! Copyright (C) 2008 Eduardo Cavazos, Slava Pestov.
! See http://factorcode.org/license.txt for BSD license.
USING: kernel system accessors namespaces splitting sequences make
USING: kernel system accessors namespaces splitting sequences
mason.config ;
IN: mason.platform
@ -10,10 +10,8 @@ IN: mason.platform
: gnu-make ( -- string )
target-os get { "freebsd" "openbsd" "netbsd" } member? "gmake" "make" ? ;
: boot-image-arch ( -- string )
target-cpu get dup "ppc" = [ target-os get "-" append prepend ] when ;
: boot-image-name ( -- string )
[
"boot." %
target-cpu get "ppc" = [ target-os get % "-" % ] when
target-cpu get %
".image" %
] "" make ;
"boot." boot-image-arch ".image" 3append ;

View File

@ -20,7 +20,8 @@ IN: mason.updates
= not ;
: new-image-available? ( -- ? )
boot-image-name need-new-image? [ download-my-image t ] [ f ] if ;
boot-image-name need-new-image?
[ boot-image-arch download-image t ] [ f ] if ;
: new-code-available? ( -- ? )
updates-available?