Re: toolchain/47188: MKTOOLS=no broken

[Alan Barrett <apb%netbsd.org@localhost>]

The following reply was made to PR toolchain/47188; it has been noted by GNATS.

From: Alan Barrett <apb%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: toolchain/47188: MKTOOLS=no broken
Date: Thu, 15 Nov 2012 11:17:34 +0200

 On Tue, 13 Nov 2012, sjg%crufty.net@localhost wrote:
 >Having run:
 >
 >TOOLDIR=/var/obj/NetBSD/current/tools/NetBSD-5.99.55-x86_64 \
 >sh -x ./build.sh -m amd64 -M /var/obj/NetBSD/current/amd64/obj tools
 >
 >and then running:
 >
 >TOOLDIR=/var/obj/NetBSD/current/tools/NetBSD-5.99.55-x86_64 MKTOOLS=no \
 >sh -x ./build.sh -u -U -m amd64 -M /var/obj/NetBSD/current/amd64/obj \
 >-D /var/obj/NetBSD/current/amd64/destdir \
 >-R /var/obj/NetBSD/current/amd64/release release
 >
 >fails [...]
 
 I think there's a mistake in the above instructions.  I think that the
 problem manifests only when the two build.sh invocations use different
 obj directories, but the above instructions use the same -M option both
 times.
 
 I can replicate this problem if I pass different "-M <objdir>"
 options, but the same TOOLDIR value, to the two build.sh
 invocations, and if I use MKTOOLS=no the second time.
 
 --apb (Alan Barrett)