Hmmm, I'm specifically talking about when you have MAKEOBJDIRPREFIX set to 
something other than /usr/obj - it *almost* works, but /bin/sh uses files 
generated on-the-fly that get put in the wrong places (in the chroot'ed 
hierarchy). (ONLY when building the crunches - makeworld
runs fine.) I suppose its beating a dead horse (got around 
it with a symlink or two) but it niggles - but that 
whole environment is just too twisted to follow. :(

-----Original Message-----
From: John Baldwin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 12:10 PM
To: Gray, David W.
Cc: FreeBSD Current list
Subject: RE: more make release

On 29-Nov-00 Gray, David W. wrote:
> BTW, is it considered a bug or a feature that you MUST use /usr/obj to
> have make release work? I went in circles for quite a while before
> this out (I just didn't have much room in /usr, so was using the make env 
> variable to move the obj tree. It failed in various amusing ways whilst 
> building the crunches - in particular, the generated files for /bin/sh
> go to the right places, and the makefile setup is too tangled for my tiny
> brain.)

Feature.  make release starts off by doing an installworld into the chroot'd
area and using that area to do a cleanroom make world from which the release
bits are rolled.


John Baldwin <[EMAIL PROTECTED]> --
PGP Key:
"Power Users Use the Power to Serve!"  -

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to