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

From: Jeff Rizzo <riz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: toolchain-manager@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org
Subject: Re: toolchain/31462: NetBSD2.1RC5 ./build.sh tools give uril.h warning
Date: Sun, 9 Oct 2005 06:30:16 -0700

 On Tue, Oct 04, 2005 at 08:06:00AM +0000, greg.evans7@verizon.net wrote:
 > >Number:         31462
 > >Category:       toolchain
 > >Synopsis:       NetBSD2.1RC5 ./build.sh tools give uril.h warning
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    toolchain-manager
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Tue Oct 04 08:06:00 +0000 2005
 > >Originator:     Greg Evans
 > >Release:        Did Upgrade from 2.0.2 to 2.1RC5
 > >Organization:
 > None
 > >Environment:
 > NetBSD  3.99.9 NetBSD 3.99.9 (PISMO) #0: Mon Oct  3 19:48:12 PDT 2005  ro=
 ot@:/usr/obj/sys/arch/macppc/compile/PISMO macppc
 > >Description:
 > I upgraded from 2.0.2 to 2.1RC5 today and IIRC installed sys.tar.gz and t=
 hen did ./build.sh tools in the /usr.src directory and received a uril.h wa=
 rning. it said that I should report it to lib-bug-people@netbsd.org so I se=
 nt an email off there and was asked to file a pr. apologies for not knowing=
  more and perhaps it is my error, but I figured I should report it anyway
 > >How-To-Repeat:
 > Didn't try to repeat, but I will guess that ./build.sh tools will cause t=
 he same warning if I do it again=20
 > >Fix:
 > none. sorry, not a un*x programmer or even guru=20
 
 Can you please give more information on this?  It's not clear from your
 problem report what platform this is on, or whether you sent the report
 from the same machine you had the problem on.  (You said you installed
 2.1_RC5, but the problem report came from a machine running 3.99.9/macppc)
 (Also, please try wrapping your lines at less than 80 columns for
 better readability)
 
 I need a few more pieces of information before I can help -=20
 
 1.  the output of "uname -a" on the machine in question
 
 2.   A cut-and-paste of the actual error you saw, with the command it was
 running.  You don't need to paste the whole build.sh output, but you
 should at least paste the command you typed.
 
 
 However, I suspect that the problem may be more basic than that:  if
 the only source tarball you installed was "sys.tar.gz", you don't have
 enough files to use "./build.sh tools".   That requires _all_ of the source
 sets.  If you want to only download the kernel source (sys.tar.gz), you'll
 need to use config and make directly.
 
 +j
 --=20