Subject: Re: toolchain/16178: mkdir /usr/tools makes build fail.
To: Christos Zoulas <firstname.lastname@example.org>
From: Todd Vierling <email@example.com>
Date: 04/03/2002 10:56:29
On Wed, 3 Apr 2002, Christos Zoulas wrote:
: | : This will fail if /usr/tools exists and /usr/tools/bin fails.
: | : if [ ! -d /usr/tools/bin ]; then mkdir /usr/tools; mkdir /usr/tools/bin; fi;
: | A build log is needed here. Most such mkdir commands are already "mkdir -p".
: cd /usr/src/tools; make clean; rm -fr /usr/tools; mkdir /usr/tools; make
: fails instantly.
I do not have a machine running -current userland on a regular basis for a
couple of reasons, so just saying "do a make in src/tools" is more difficult
as a testcase. My builds are mostly build.sh nbmake-wrapper based at the
The build does not fail "instantly" (which would imply that something in
src/tools/Makefile* was busted -- in fact, it was in a subdirectory!), which
is why I requested a build log as is standard procedure. Simply noting
which *directory* it failed in would have helped considerably.
(Fortunately, you named your TOOLDIR "/usr/tools", so I dind't have to ask
the standard question to dump your mk.conf. :)
Anyway, I was able to track it down after doing recursive greps and reading
several Makefiles. You apparently beat me to it, but I dropped the "if"
part of the block, since it is now "mkdir -p", in rev. 1.5 of
-- Todd Vierling <firstname.lastname@example.org> * Wasabi & NetBSD: Run with it.
-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/