Date: Wed, 11 Aug 2004 19:42:38 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Ruslan Ermilov <ru@freebsd.org> Cc: current@freebsd.org Subject: Re: World broken in stage 1.1 Message-ID: <20040811094238.GB423@cirb503493.alcatel.com.au> In-Reply-To: <20040811080350.GK80234@ip.net.ua> References: <20040810231044.GA70020@xor.obsecurity.org> <20040811061202.GA80234@ip.net.ua> <20040811065912.GA95263@xor.obsecurity.org> <20040811080350.GK80234@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2004-Aug-11 11:03:50 +0300, Ruslan Ermilov wrote:
>Trying to set MAKEOBJDIRPREFIX in /etc/make.conf and attempting to buildworld
>RELENG_4 on a 4.x machine similarly fails right away.
I have a script that run on RELENG_4 and does
make MAKEOBJDIRPREFIX=/usr/obj/k7 CPUTYPE=k7 buildworld >buildworld.k7 2>&1 &
make MAKEOBJDIRPREFIX=/usr/obj/i486 CPUTYPE=i486 buildworld >buildworld.i486 2>&1 &
make MAKEOBJDIRPREFIX=/usr/obj/i586 CPUTYPE=i586/mmx buildworld >buildworld.i586 2>&1 &
This worked perfectly when I tried it on 1st August - at least the
system compiled, installed and has been running since last weekend. I
have another -STABLE system that has MAKEOBJDIRPREFIX in
/etc/make.conf and runs build{world,kernel} happily every night. I
admit I haven't tried using MAKEOBJDIRPREFIX on -CURRENT lately.
Overall, I find it annoying that it is no longer possible to embed all
the buildworld customisations in /etc/make.conf.
--
Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040811094238.GB423>