Re: Building in a read only repository

[Tyler Retzlaff <rtr%omicron-persei-8.net@localhost>]

Hi,

On Wed, Jun 04, 2014 at 12:09:28PM -0400, D'Arcy J.M. Cain wrote:
> On Wed, 04 Jun 2014 04:43:12 +1000
> matthew green <mrg%eterna.com.au@localhost> wrote:
> > > WRKDIRPREFIX = /usr/obj
> > > BUILDIR = /usr/obj/build
> > > WRKOBJDIR = /usr/obj
> > > TOOLDIR = /usr/obj/tools
> > > BSDOBJDIR = /usr/obj
> > > RELEASEDIR = /usr/obj/release   
> > > DESTDIR = /usr/obj/destdir      
> > > 
> > > I then go into /usr/src and build everything.  The following two
> > > commands work fine:
> > > 
> > > # ./build.sh -M /usr/obj tools
> > > # ./build.sh -M /usr/obj kernel=GENERIC

Is this all mk.conf & build.sh?

For command line simplicity I typically also add at least the following
to mk.conf

MKOBJDIRS?=     yes
MKUNPRIVED?=    yes

I didn't notice -U being passed to your build.sh and if your source is
read-only either that or MKUNPRIVED yes in mk.conf would be necessary no?

Also, not having MKOBJDIRS yes might be what is exploding your current
build.

> > 
> > setting -M to the same base-dir as all of the base seems like
> > it might be causing your problem.
> I assume that that doesn't matter if I am only building for my own
> system.

I think this is okay.

> > 
> > perhaps try removing BSDOBJDIR.

I don't know about this, I can just say I don't set it myself.

rtr