On Dec 08, "Steve Kargl" wrote: > On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > > Hi, > > > > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > > out here: > > > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So > > building shared library libmagic.so.1 > > Segmentation fault (core dumped) > > *** Error code 139 > > > > You need to back out the recent changes to make(1). > In your supfile file that you use with cvsup, set > > *default date=2004.11.08.00.00.00 > src-usrbin > > cd /usr/src/usr.bin/make > make > make install > > PS: surprising the broken make(1) actually works for building > a new make(1). 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? Befuddled in BerkeleyReceived on Thu Dec 09 2004 - 17:10:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:24 UTC