Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Still having build problems with CURRENT




To: Kimi <kimimeister%gmail.com@localhost>

Subject: Re: Still having build problems with CURRENT

From: David Laight <david%l8s.co.uk@localhost>

Date: Sun, 13 Jan 2008 18:05:57 +0000


On Sun, Jan 13, 2008 at 03:14:34PM +0000, Kimi wrote:
> 
> I used to have the source code which was obtained by using csup and
> put under the right place of /usr/src on my local discs & same goes
> for /usr/obj. now I noticed there had been some changes in regards to
> a read-only /usr/src which is great, so I have been nfs mounting both
> /usr/src and /usr/obj, created a mk.conf  and placing both MAKEOBJDIR
> = /usr/obj and MAKEOBJDIRPREFIX = /usr/obj in there.

MAKEOBJDIR and MAKEOBJDIRPREFIX have to be in the environment when
make is started - since they are acted on before any makefiles are read.

You really need to use build.sh, eg:

I use a shell script to run build.sh that ends up doing:

exec ./build.sh -x -X ../xsrc -N $N ${j:+-j $j} -T $tools -u -U -D $destdir -O 
$objdir -R $releasedir "$@"

        David

-- 
David Laight: david%l8s.co.uk@localhost



Follow-Ups:

Re: Still having build problems with CURRENT
From: Kimi


References:

Still having build problems with CURRENT
From: Kimi




Prev by Date: Re: azalia: no audio on acer aspire 5310

Next by Date: TCP segmentation offload broken on bge

Previous by Thread: Re: Still having build problems with CURRENT

Next by Thread: Re: Still having build problems with CURRENT

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index