Subject: Re: Problem remains with build.sh *not* installing new binaries
To: Xavier HUMBERT <firstname.lastname@example.org>
From: Jaromir Dolecek <email@example.com>
Date: 07/19/2002 21:43:30
This is what happens:
1. build.sh sets environment variable DESTDIR to what was specified by -D
2. DESTDIR is passed with other environ to spawned make(1), which
sets it's own make DESTDIR accordingly
3. when a program directory is entered, it's <bsd.foo.mk> is read;
this includes pulling in <bsd.own.mk> and thus your /etc/mk.conf
4. your /etc/mk.conf had
i.e. it inconditionally overrode any previous setting
5. for rest of processing (compiling, installing, whatever), make(1)'s
DESTDIR was set to /usr/build
In other words, you managed to hang yourself on the rope provided
by build.sh/make mechanisms :)
One possible fix is to change the DESTDIR setting in your /etc/mk.conf to:
in your /etc/mk.conf, so that it would only provide default, not
override other settings.
Xavier HUMBERT wrote:
> You wrote :
> > Currently, build.sh DOES NOT override mk.conf for DESTDIR.
> WHAT ?!??!?
> I never seen that written anywhere (otherwise, I'll immediately start
> lashing myself with brambles)
> Do you mean that *this*
> > [xavier@arnor src]$ ./build.sh -h
> > Usage:
> > [...snip...]
> > -D: set DESTDIR to dest
> is not true ?
> Oh my God ! I can't believe this !
> Do you mean that my boxes are not properly updated since new toolchain
> is out ?
> I can be that, build.sh shows me
> > ===> DESTDIR path: /
> > ===> TOOLDIR path: /usr/tools
> when called with "-D /". It even complains, if I erroneously leave a
> "-d" flag wit "-D /"
> Tell me the problkem is elsewhere, before I kill myself !
> Thanks, anyway, I'll correct mk.conf asap on all my boxes ...
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/Ports/i386/ps2.html
-=- We should be mindful of the potential goal, but as the tantric -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow. Do not let this distract you.'' -=-