Date: Sat, 27 Mar 2021 12:57:27 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-stable stable <freebsd-stable@freebsd.org> Subject: Re: build failed for 12.2-p5 Message-ID: <392639F2-04C0-4953-B706-B9F27CD3826B@FreeBSD.org> In-Reply-To: <4dd371b4-7135-fc0d-ce62-ae68467cb289@quip.cz>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 27 Mar 2021, at 12:39, Miroslav Lachman <000.fbsd@quip.cz> wrote: > > I compiled 12.2-p4 from sources 2 days ago but any attempt to build update for 12.2-p5 ends with error. > > Previous build was done on 11.4: > > # cd /usr/src/ > # git clone https://github.com/freebsd/freebsd.git -b releng/12.2 ./ > # make buildworld > # make buildkernel > > 11.4 machine was upgraded to 12.2 (I did also run mergemaster) so now I have FreeBSD 12.2-RELEASE-p4 amd64 GENERIC > > # cd /usr/src/ > # git pull --ff-only > # make -DNO_CLEAN buildworld > > it ends with the following error > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 xinstall /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin/install > sh /usr/src/tools/install.sh -o root -g wheel -m 444 install.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/install.debug > *** Signal 11 You'll need to debug the core dump to see what it segfaulted on. In this case, I would first suspect the hardware. Run a full memtest86 for 24 hours to see if it results in any errors. > Stop. > make[3]: stopped in /usr/src/usr.bin/xinstall > *** Error code 1 > > Usr: 437.951s Krnl: 15.620s Totl: 7:48.92s CPU: 96.7% swppd: 0 I/O: 55800+84576 > > I tried without -DNO_CLEAN but it failed again > > sh /usr/src/tools/install.sh -o root -g wheel -m 444 make-roken.debug /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib/debug/usr/bin/make-roken.debug > ===> kerberos5/lib/libroken (obj,all,install) > [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] > make-roken > roken.h > *** Signal 11 This won't help you at all, if the first build failed then there is no reason the next will work. If your hardware is faulty then you will only run into random errors like this, which is why I would suggest checking your hardware first. Now, the roken.h file that was produced is obviously prematurely cut off, which is almost certainly the cause for the next failure: > # make -DNO_CLEAN buildkernel > > cc -O2 -pipe -fno-common -I/usr/src/crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/include -g -MD -MF.depend.copyhostent.o -MTcopyhostent.o -std=gnu99 -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/crypto/heimdal/lib/roken/copyhostent.c -o copyhostent.o > /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:1: error: unknown type name > 'ROKEN_LIB_FUNCTION' > ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL > ^ > /usr/src/crypto/heimdal/lib/roken/copyhostent.c:42:51: error: expected ';' after top level > declarator > ROKEN_LIB_FUNCTION struct hostent * ROKEN_LIB_CALL > ^ > ; Since the roken.h file is bad, it won't compile. Delete the bad roken.h, or maybe your entire /usr/obj, and after your hardware turns out to be okay, try again. -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iFwEARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCYF8dpwAKCRCwXqMKLiCW o/ImAJUTYzs/owqAbBMer7YnwuK7XaaWAKD/L9KgMttXNcwAZTRtzfrDspQPzw== =DLsM -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?392639F2-04C0-4953-B706-B9F27CD3826B>