Date: Tue, 22 Jun 2021 11:18:21 +0200 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: stable@freebsd.org Subject: Re: [releng/13.0] error during installworld Message-ID: <aa219cc5-72f8-07b2-43b7-62943315f32d@plan-b.pwste.edu.pl> In-Reply-To: <3877o092-527-554s-3n1n-58r27r7p6522@negpncvgny.hn> References: <sr77qs2-907s-577o-2q62-8s6174q9pr84@negpncvgny.hn> <ffc6e222-fe62-2186-1198-0b56fe9bee78@plan-b.pwste.edu.pl> <3877o092-527-554s-3n1n-58r27r7p6522@negpncvgny.hn>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pElrp7Tqxz3SWbRdgmx7x48y4Rx4cIe7T
Content-Type: multipart/mixed; boundary="3kbTdXGC9WJtFA4AsldeDvGgGPoKY1Kfr";
protected-headers="v1"
From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
To: stable@freebsd.org
Message-ID: <aa219cc5-72f8-07b2-43b7-62943315f32d@plan-b.pwste.edu.pl>
Subject: Re: [releng/13.0] error during installworld
References: <sr77qs2-907s-577o-2q62-8s6174q9pr84@negpncvgny.hn>
<ffc6e222-fe62-2186-1198-0b56fe9bee78@plan-b.pwste.edu.pl>
<3877o092-527-554s-3n1n-58r27r7p6522@negpncvgny.hn>
In-Reply-To: <3877o092-527-554s-3n1n-58r27r7p6522@negpncvgny.hn>
--3kbTdXGC9WJtFA4AsldeDvGgGPoKY1Kfr
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
W dniu 22.06.2021 o=C2=A010:51, Yaroslav Shvets pisze:
> Hello Marek.
>=20
> On Tue, 22 Jun 2021, 11:04, you wrote:
>=20
>> W dniu 22.06.2021 o=C2=A008:30, Yaroslav Shvets pisze:
>>> Hello All.
>>>
>>> I have successfully updated os from the sources from releng/12.2 to
>>> releng/13.0.
>>> But when reinstalling the world from releng/13.0,
>>> I get the error during installworld:
>>>
>>> installworld.log:
>>> -- cut --
>>> =3D=3D=3D> stand/i386/mbr (install)
>>> install=C2=A0=C2=A0 -o root -g wheel -m 444=C2=A0=C2=A0 mbr /boot/mbr=
>>> =3D=3D=3D> stand/i386/pmbr (install)
>>> install=C2=A0=C2=A0 -o root -g wheel -m 444=C2=A0=C2=A0 pmbr /boot/pm=
br
>>> =3D=3D=3D> stand/i386/boot0 (install)
>>> install=C2=A0=C2=A0 -o root -g wheel -m 444=C2=A0=C2=A0 boot0 /boot/b=
oot0
>>> =3D=3D=3D> stand/i386/boot0sio (install)
>>> install=C2=A0=C2=A0 -o root -g wheel -m 444=C2=A0=C2=A0 boot0 /boot/b=
oot0sio
>>> =3D=3D=3D> stand/i386/boot2 (install)
>>> btxld -v -E 0x2000 -f bin -b
>>> /usr/obj/usr/src/amd64.amd64/stand/i386/btx/btx/btx -l boot2.ldr=C2=A0=
-o
>>> boot2.ld -P 1 boot2.bin
>>> make[6]: exec(btxld) failed (No such file or directory)
>>> *** Error code 1
>>>
>>> Stop.
>>> make[6]: stopped in /usr/src/stand/i386/boot2
>>> *** Error code 1
>>>
>>> Stop.
>>> make[5]: stopped in /usr/src/stand/i386
>>> *** Error code 1
>>>
>>> Stop.
>>> make[4]: stopped in /usr/src/stand
>>> *** Error code 1
>>>
>>> Stop.
>>> make[3]: stopped in /usr/src
>>> *** Error code 1
>>>
>>> Stop.
>>> make[2]: stopped in /usr/src
>>> *** Error code 1
>>>
>>> Stop.
>>> make[1]: stopped in /usr/src
>>> *** Error code 1
>>>
>>> Stop.
>>> make: stopped in /usr/src
>>> -- cut --
>>>
>>> /etc/src.conf is absent
>>>
>>> /etc/make.conf:
>>> -- cut --
>>> NO_GUI=3D=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 true
>>> NO_X=3D=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 t=
rue
>>> OPTIONS_UNSET=3D=C2=A0 GUI
>>> OPTIONS_UNSET=3D=C2=A0 X11
>>>
>>> # with SASLv2:
>>> SENDMAIL_CFLAGS=3D-I/usr/local/include -DSASL=3D2
>>> SENDMAIL_LDFLAGS=3D-L/usr/local/lib
>>> SENDMAIL_LDADD=3D-lsasl2
>>> -- cut --
>>>
>>> What to do now?
>>>
>>
>> It became quite a common failure (race) lately for parallel builds wit=
h
>> NO_CLEAN and nullfs mounted OBJ dir. In my case rebuilding world with
>> only one job helps. You can also ignore this and install the world
>> anyway.
>=20
> Thank a lot for your answer!
>=20
> Indeed, /usr/obj is mounted by nullfs.
> I will try to rebuild the world in one thread.
>=20
> But how can i ignore the error and continue the installation of the wor=
ld?
> Is there some kind of flag for the Makefile?
>=20
Please compare make(1). "make -i installworld" will do the job, but it
should be considered as a temporary only solution which might lead to
some serious failures when abused.
There was a thread about this issue in 13-BETA3 on the freebsd-stable@
mailing list, but I can't give you the reference since archives from
February 2021 disappeared. For the first time I have fallen into this
about 2 years (January 2020) on CURRENT and asked for help on
freebsd-current@. At that time keveans@ suggested such a patch:
diff --git a/stand/i386/Makefile b/stand/i386/Makefile
index a9d402acf60..24255eefabf 100644
--- a/stand/i386/Makefile
+++ b/stand/i386/Makefile
@@ -4,7 +4,10 @@ NO_OBJ=3Dt
.include <bsd.init.mk>
-SUBDIR.yes=3D mbr pmbr boot0 boot0sio btx boot2 cdboot gptboot \
+# Almost everything else here relies on btxldr, so we must make sure
it's built
+# before everything else proceeds so we don't end up building against a
stale
+# btxldr and ending up with a build-during-install scenario.
+SUBDIR.yes=3D btx .WAIT mbr pmbr boot0 boot0sio boot2 cdboot gptboot =
\
isoboot libi386
This patch worked back at that time. Unfortunately the thread on the
mailing list disappeared, so I can't give you the reference.
--=20
Marek Zarychta
--3kbTdXGC9WJtFA4AsldeDvGgGPoKY1Kfr--
--pElrp7Tqxz3SWbRdgmx7x48y4Rx4cIe7T
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsB5BAABCAAjFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAmDRqt0FAwAAAAAACgkQdZ/s//1SjSxw
Awf8C9V9qkoS4Ye6VO3l0bmAm4iK3P7XAA7Rw86gCuB42LHt/flH1ydS2KLVSiIHlLetKnL4rxPo
Xq3tl6fZDLSpaYmf88Y/tiDGodgirzDpb4vmoX1OoM2AkV6/LM4H9VSXsmJIY0N+i5ZckAqatvsm
Q8icXC6idJ5y8RLdEZM+AGAwpdbeocfkyh8bmLJGK/zoqLRwWd3w6Voe2zBr1csBU/Yx8ybNGedv
I5ZgPeyw1OZLJAzaqseB7bk49kfNFFB3/qIF8XtFismpi/qSk5MOZpAJE9XPGn2fEQfYRnugP7A2
GFeg8Zj6j7/zmdlKe3xyAbg5i+7TgnBoDqasnyKvaw==
=ynBD
-----END PGP SIGNATURE-----
--pElrp7Tqxz3SWbRdgmx7x48y4Rx4cIe7T--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aa219cc5-72f8-07b2-43b7-62943315f32d>