Date: Thu, 9 Dec 2004 10:28:16 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Mike Hunter <mhunter@ack.Berkeley.EDU> Cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) Message-ID: <20041209182816.GA27303@troutmask.apl.washington.edu> In-Reply-To: <20041209181034.GA16160@ack.Berkeley.EDU> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209002939.GB7272@troutmask.apl.washington.edu> <20041209181034.GA16160@ack.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 09, 2004 at 10:10:34AM -0800, Mike Hunter wrote: (snip) > > Ugh. I tried cvsupping as you suggested, but it gave the same error. This > morning I cvsup'd again after make was fixed (thanks!), and it *still* gives > the same error. I don't think my installed /usr/bin/make is being updated. > > I forgot to md5 the original make, but this is from this morning's fixed-make > sources: > > bash-2.05b# cd /usr/src/usr.sbin/make > bash-2.05b# make > ... > job.o(.text+0x2973): In function `Job_Init': > : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() > gzip -cn /usr/src/usr.bin/make/make.1 > make.1.gz > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > bash-2.05b# find /usr/obj -type f -name make | xargs -L 1 md5 > MD5 (/usr/obj/usr/src/make.amd64/usr/src/usr.bin/make/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/make.amd64/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/usr.bin/make/make) = 0e719846f3f245fa7aa7d3aa2dca0bfd > bash-2.05b# make install > install -s -o root -g wheel -m 555 make /usr/bin > install -o root -g wheel -m 444 make.1.gz /usr/share/man/man1 > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > > Why doesn't /usr/bin/make change? Let me guess, there's a bug in make? :| > > I am trying again after copying /usr/obj/usr/src/usr.bin/make/make over > /usr/bin/make by hand. Am I missing something here? Also, what's the > make.amd64 directory about, and why are those make binaries also different? > I'm not sure what is causing your problem, I will note that I do not have a make.amd64 directory. This suggests to me that your src tree may be messed up. I'm running -current while you appear to be using RELENG_5 perhaps you need to install from make.amd64 instead of from make. One other thing to do. Clean out your trees. rm -rf /usr/obj cd /usr/src make cleandir && make cleandir (the 2nd cleandir my be unnecessary) make buildworld yada yada -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041209182816.GA27303>