Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <019a01c2ca1e$1cb68af0$78d96f83@pomello> From: "Max Bowsher" To: "Christos Dritsas" Cc: References: <3E3C040C DOT 7000204 AT sonic DOT net> <014001c2ca17$d42f8da0$78d96f83 AT pomello> <3E3C04EA DOT 7060308 AT sonic DOT net> <015a01c2ca19$e6fd5370$78d96f83 AT pomello> <3E3C0B71 DOT 7020907 AT sonic DOT net> Subject: Re: Cygwin Compile of NetBSD 1.6 Date: Sat, 1 Feb 2003 18:16:59 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > Max Bowsher wrote: >> The output you posted looks like a standard autoconf-type configure. >> I think that the config.log should be created in the current working >> directory when configure is executed. I can't imagine how it could >> not be created. This build.sh doesn't locate the temporary build >> stuff in /tmp, or somewhere, does it? Christos Dritsas wrote: > Not too sure, here is the relevent code from the build.sh script > though: > > # Build bootstrap nbmake if needed. > if $do_rebuildmake; then > $runcmd echo "===> Bootstrapping nbmake" > tmpdir="${TMPDIR-/tmp}/nbbuild$$" Aha. It does put it elsewhere. > > $runcmd mkdir "$tmpdir" || bomb "cannot mkdir: $tmpdir" > trap "cd /; rm -r -f \"$tmpdir\"" 0 And it removes it all when the script exits. > I did also look for the config.log under $TOP/tools/make/ but found > nothing. Now you know why. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/