Re: Compiling the current source code

[Johan Ihren <johani%johani.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Alan,

On 7 Aug 2008, at 18:51, Alan Barrett wrote:

> On Thu, 07 Aug 2008, Erik Bertelsen wrote:
> > After your changes to build.sh in rev. 1.191 of Aug 5th it appears
> > that it is now mandatory to use -O or -M with build.sh.
>
> Yes, but only if build.sh can't guess where you want the object
> directory to be.
>
> > I feel much more comfortable having set the paths to the source and
> > object directories in /etc/mk.conf rather than specifying them in  
> > each
> > call to build.sh.
>
> Setting it in make.conf not supposed to be possible.  make(1)  
> internally
> decides which object directory to use before it reads /etc/mk.conf.
>
> > My question really is whether it is intentional that using BSDOBJDIR
> > and BSDSRCDIR in /etc/mk.conf has stopped working ?
>
> No, that was not intentional.  Are you sure that it worked before?

I'm seeing the same thing and I'm 100% sure it used to work. I don't  
use mk.conf, I source a prep script where I define BSDOBJDIR et al as  
functions of arch and date. I also "mkdir -p $BSDOBJDIR [et al]".

This no longer works.

> What do you get from (cd ${SRCDIR}; make -V __usrobjdir; make -V  
> _SRC_TOP_),

> and is your source in /usr/src or not?

alenny:current/src#(echo ${SRCDIR}; make -V __usrobjdir; make -V  
_SRC_TOP_)

${BSDOBJDIR}${USR_OBJMACHINE:D.${MACHINE}}
/usr/store/source/netbsd/current/src

Regards,

Johan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFIm+DCKJmr+nqSTbYRAi1uAKCPneIiRVfVi3v9Y7GnCvmxAq24cQCeJlVf
/YFWQo/cebzcf2b6uImLg2k=
=Y0I2
-----END PGP SIGNATURE-----