Date: Tue, 1 Dec 2015 14:51:04 -0800 From: Bryan Drewery <bdrewery@FreeBSD.org> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: HELP! libelf.so: no such file or directory Message-ID: <565E2458.6000505@FreeBSD.org> In-Reply-To: <565E2341.5010301@FreeBSD.org> References: <20151201233145.2b9d7ee5.ohartman@zedat.fu-berlin.de> <20151201233828.1e03c5c6.ohartman@zedat.fu-berlin.de> <565E2341.5010301@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hokQF4xWsf033hTM9d7MG4TnD0BwgQ0Gl Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 12/1/2015 2:46 PM, Bryan Drewery wrote: > On 12/1/2015 2:38 PM, O. Hartmann wrote: >> Am Tue, 1 Dec 2015 23:31:45 +0100 >> "O. Hartmann" <ohartman@zedat.fu-berlin.de> schrieb: >> >>> >>> Just a few moments ago, I installed via buildworld/buildkernel a new = CURRENT, then did >>> "make delete-old-libs" and by that, libelf.so.2 got killed! >>> >>> After that, I'm unable to build any world to salvage the problem! Mom= ents later, I did >>> the same procedure on other CURRENT - but in the meanwhile, the obscu= re deleteing of >>> libelf.so.2 didn't happen again when issue make delete-old-libs. What= is that? >>> >>> More important than to know what shit happened is: how to repair the = system? How's >>> FreeBSD source system to bootstrap itself again to provide libelf.so.= 2? It seems, that >>> libelf.so.2 is necessary (nm, for instance) or linker scripts to inst= all lib. Somehow >>> this is weird ... and leave those who got trapped by someone eleses m= istakes floating >>> dead in the water ... >>> >>> >>> >>> oh=20 >> >> Great ... CURRENT, at revision 291620. >> >> [...] >> >> =3D=3D=3D> sys/boot/i386/boot0sio (all) >> --- all_subdir_libexec --- >> make[4]: make[4]: don't know how to make /Versions.def. Stop >> >> make[4]: stopped in /usr/src/libexec/rtld-elf >> >=20 > This is a mistake I just made. Fixing it. >=20 Should be ok now after r291622. --=20 Regards, Bryan Drewery --hokQF4xWsf033hTM9d7MG4TnD0BwgQ0Gl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWXiRYAAoJEDXXcbtuRpfPpVcH/Akwt9kNf/GO6gSLUpQ4gQY7 ZRWXRdPLQHS6Zh1cJv1EaxtQenBJ0tZ8Kcw2ilCfcfxk26hF927kUlpS+ZpD2sEH dE/Zt0KCP72E5yTsdil3wVdZ8WfH36ZteXkx9Wf8mUjeMWHPET3OjSYl6NOcSB5U cAEpxsIsU95ma7GBp+9U9iI15cBU3Wt+1gkHNW6TAKNDve3O0TTqtVVDREp9JBmd ndNjy0iilBHl27VGac4/gBrdis9j37L8qCX3GRTjCqcXdlKT1VdQeCUUcL2ilWzu 9LS0F5dnEXECfZ2oadm8S8/cHVCylXf/kVkRUAYj9O+Hpp5IvGrvy2lhdEdb7+M= =D7h2 -----END PGP SIGNATURE----- --hokQF4xWsf033hTM9d7MG4TnD0BwgQ0Gl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?565E2458.6000505>