NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



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

From: George Georgalis <george%galis.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: toolchain-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	netbsd-bugs%netbsd.org@localhost, David Holland <dholland%netbsd.org@localhost>
Subject: Re: toolchain/43272: no nbsed after first release build
Date: Mon, 12 Sep 2016 14:17:24 -0700

 --001a113deb42cebc2d053c56053b
 Content-Type: text/plain; charset=UTF-8
 
 Hi - I confirmed last week, this bug is not present in supported releases
 (netbsd-7-0 and netbsd-6-0), so there is no reason to keep this issue open.
 Thanks! -George
 
 
 On Sat, Jan 21, 2012 at 11:10 PM, David Holland <dholland%netbsd.org@localhost> wrote:
 
 > 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
 >
 >
 
 
 -- 
 George Georgalis, (415) 894-2710, http://www.galis.org/
 
 --001a113deb42cebc2d053c56053b
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr">Hi - I confirmed last week, this bug is not present in sup=
 ported releases (netbsd-7-0 and netbsd-6-0), so there is no reason to keep =
 this issue open. Thanks! -George<br><br><div class=3D"gmail_extra"><br><div=
  class=3D"gmail_quote">On Sat, Jan 21, 2012 at 11:10 PM, David Holland <spa=
 n dir=3D"ltr">&lt;<a href=3D"mailto:dholland%netbsd.org@localhost"; target=3D"_blank">=
 dholland%netbsd.org@localhost</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
 te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
 ><span class=3D"">The following reply was made to PR toolchain/43272; it ha=
 s been noted by GNATS.<br>
 <br>
 From: David Holland &lt;<a href=3D"mailto:dholland%netbsd.org@localhost";>dholland@net=
 bsd.org</a>&gt;<br>
 </span>To: George Georgalis &lt;<a href=3D"mailto:george%galis.org@localhost";>george@=
 galis.org</a>&gt;<br>
 Cc: <a href=3D"mailto:gnats-bugs%netbsd.org@localhost";>gnats-bugs%netbsd.org@localhost</a><br>
 <span class=3D"">Subject: Re: toolchain/43272: no nbsed after first release=
  build<br>
 </span>Date: Sun, 22 Jan 2012 07:07:54 +0000<br>
 <div class=3D"HOEnZb"><div class=3D"h5"><br>
 =C2=A0On Fri, Jan 20, 2012 at 01:50:27AM -0800, George Georgalis wrote:<br>
 =C2=A0 &gt; Um, I replied to gnats and dholland (below),I have no reply or =
 record<br>
 =C2=A0 &gt; of my response in gnats, and now I have reminders to reply???<b=
 r>
 <br>
 =C2=A0hmm...<br>
 <br>
 =C2=A0oh I see:<br>
 <br>
 =C2=A0 &gt; Subject: toolchain/43272 no nbsed after first release build<br>
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
 =A0 =C2=A0 =C2=A0 =C2=A0 :<br>
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
 =A0 =C2=A0 =C2=A0 ^^^^<br>
 <br>
 =C2=A0you need a colon in there for gnats to pay attention, I think :(<br>
 =C2=A0also (maybe more importantly) the subject needs to begin with &quot;R=
 e:&quot;<br>
 =C2=A0I&#39;m a bit more behind than usual with gnats traffic right now :(<=
 br>
 <br>
 <br>
 =C2=A0As for the problem - the order of tools is listed in src/tools/Makefi=
 le:<br>
 <br>
 =C2=A0 =C2=A0 SUBDIR=3D host-mkdep .WAIT compat .WAIT \<br>
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0binstall .WAIT mktemp .WAIT sed .W=
 AIT \<br>
 <br>
 =C2=A0so even in a parallel build sed should come immediately after mktemp,=
 <br>
 =C2=A0and once it gets that far, there should be a nbsed and it should be<b=
 r>
 =C2=A0runnable.<br>
 <br>
 =C2=A0What I meant to ask for was a transcript of the part of the tools<br>
 =C2=A0build where it&#39;s supposed to be building sed. Almost certainly wh=
 at&#39;s<br>
 =C2=A0happening is that something fails, so sed doesn&#39;t get built and/o=
 r<br>
 =C2=A0doesn&#39;t get installed, but for some reason this doesn&#39;t cause=
  the<br>
 =C2=A0build to stop like it should. Often in such situations a second run<b=
 r>
 =C2=A0will succeed because the failure on the first run leaves behind a<br>
 =C2=A0partial file so the step that didn&#39;t work doesn&#39;t get run aga=
 in.<br>
 <br>
 =C2=A0What we need to figure out is what happened.<br>
 <br>
 =C2=A0There&#39;s no need to try multiple branches or anything -- almost<br=
 >
 =C2=A0certainly there&#39;s one thing wrong, so test on whatever&#39;s most=
 <br>
 =C2=A0convenient. Once we figure out what&#39;s broken we can decide where =
 and<br>
 =C2=A0in how many places to apply the fix...<br>
 <br>
 =C2=A0--<br>
 =C2=A0David A. Holland<br>
 =C2=A0<a href=3D"mailto:dholland%netbsd.org@localhost";>dholland%netbsd.org@localhost</a><br>
 <br>
 </div></div></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=
 =3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
 iv>George Georgalis, (415) 894-2710, <a href=3D"http://www.galis.org/"; targ=
 et=3D"_blank">http://www.galis.org/</a></div></div></div>
 </div></div>
 
 --001a113deb42cebc2d053c56053b--
 


Home | Main Index | Thread Index | Old Index