Re: toolchain/43272: no nbsed after first release build

[David Holland <dholland%netbsd.org@localhost>]

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

From: David Holland <dholland%netbsd.org@localhost>
To: George Georgalis <george%galis.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: toolchain/43272: no nbsed after first release build
Date: Sun, 22 Jan 2012 07:07:54 +0000

 On Fri, Jan 20, 2012 at 01:50:27AM -0800, George Georgalis wrote:
  > Um, I replied to gnats and dholland (below),I have no reply or record
  > of my response in gnats, and now I have reminders to reply???
 
 hmm...
 
 oh I see:
 
  > Subject: toolchain/43272 no nbsed after first release build
                            :
                          ^^^^
 
 you need a colon in there for gnats to pay attention, I think :(
 also (maybe more importantly) the subject needs to begin with "Re:"
 I'm a bit more behind than usual with gnats traffic right now :(
 
 
 As for the problem - the order of tools is listed in src/tools/Makefile:
 
    SUBDIR= host-mkdep .WAIT compat .WAIT \
           binstall .WAIT mktemp .WAIT sed .WAIT \
 
 so even in a parallel build sed should come immediately after mktemp,
 and once it gets that far, there should be a nbsed and it should be
 runnable.
 
 What I meant to ask for was a transcript of the part of the tools
 build where it's supposed to be building sed. Almost certainly what's
 happening is that something fails, so sed doesn't get built and/or
 doesn't get installed, but for some reason this doesn't cause the
 build to stop like it should. Often in such situations a second run
 will succeed because the failure on the first run leaves behind a
 partial file so the step that didn't work doesn't get run again.
 
 What we need to figure out is what happened.
 
 There's no need to try multiple branches or anything -- almost
 certainly there's one thing wrong, so test on whatever's most
 convenient. Once we figure out what's broken we can decide where and
 in how many places to apply the fix...
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost