Skip site navigation (1)Skip section navigation (2)
Date:      13 May 2003 22:36:04 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
To:        Stijn Hoop <stijn@win.tue.nl>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: make release and various make.conf's
Message-ID:  <4465oei7aj.fsf@be-well.ilk.org>
In-Reply-To: <20030512141557.GC45707@pcwin002.win.tue.nl>
References:  <20030512141557.GC45707@pcwin002.win.tue.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Stijn Hoop <stijn@win.tue.nl> writes:

> I want to build a release that's as pristine as possible. Therefore
> I wanted to use a separate make.conf (A) for the initial chroot installation
> 'make buildworld', and a separate make.conf (B) for the 'make release' step.
> As the host's /etc/make.conf has options that are not appropriate for
> building the initial chroot install, make.conf (A) cannot be /etc/make.conf.
> 
> So I tried to build the chroot install with
> 
> # env __MAKE_CONF=/freebsd/etc/make.conf.host make buildworld
> 
> which succeeded. Then I tried to make the release but there I ran into
> a problem -- I needed to specify the above make.conf.host in the __MAKE_CONF
> variable in order for the initial 'installworld' to succeed -- but then I
> couldn't specify a __MAKE_CONF for the release build!
> 
> Is there a way to accomplish what I want?

I believe the release engineers normally use a jail(8) for this purpose.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4465oei7aj.fsf>