From owner-freebsd-current@freebsd.org Fri Aug 26 20:40:02 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59176B74951; Fri, 26 Aug 2016 20:40:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 35995991; Fri, 26 Aug 2016 20:40:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 27E16173F; Fri, 26 Aug 2016 20:40:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id D5B2623824; Fri, 26 Aug 2016 20:40:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id SKa1yxgjJYbL; Fri, 26 Aug 2016 20:39:59 +0000 (UTC) Subject: Re: NanoBSD install phase failing for releng/11 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com C47BA2381E To: Guido Falsi , freebsd-stable References: <537b0b16-bda0-c7c1-d771-02a34371397a@FreeBSD.org> <6548a644-dc36-baf5-c6af-78a469d38ee4@FreeBSD.org> Cc: FreeBSD CURRENT From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <2d9c5c20-9504-5d29-80e2-c00a850630b7@FreeBSD.org> Date: Fri, 26 Aug 2016 13:40:00 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <6548a644-dc36-baf5-c6af-78a469d38ee4@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x87c541BtgFlICpFhANrGvIDf8QqPVdsw" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Aug 2016 20:40:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --x87c541BtgFlICpFhANrGvIDf8QqPVdsw Content-Type: multipart/mixed; boundary="cf7ghGa1b9WxsAbN0XsVw6c6VBTp9MCcE" From: Bryan Drewery To: Guido Falsi , freebsd-stable Cc: FreeBSD CURRENT Message-ID: <2d9c5c20-9504-5d29-80e2-c00a850630b7@FreeBSD.org> Subject: Re: NanoBSD install phase failing for releng/11 References: <537b0b16-bda0-c7c1-d771-02a34371397a@FreeBSD.org> <6548a644-dc36-baf5-c6af-78a469d38ee4@FreeBSD.org> In-Reply-To: <6548a644-dc36-baf5-c6af-78a469d38ee4@FreeBSD.org> --cf7ghGa1b9WxsAbN0XsVw6c6VBTp9MCcE Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 8/24/2016 10:46 AM, Bryan Drewery wrote: > On 8/24/16 7:55 AM, Bryan Drewery wrote: >> On 8/22/2016 4:08 AM, Guido Falsi wrote: >>> Hi, >>> >>> While building a NanoBSD image using releng/11 sources I got this err= or >>> message: >>> >>> =3D=3D=3D> lib/libc++ (install) >>> install -C -o root -g wheel -m 444 libc++.a >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/ >>> install -s -o root -g wheel -m 444 libc++.so.1 >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/ >>> install -S -C -o root -g wheel -m 444 libc++.ld >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/libc++.so >>> =3D=3D=3D> lib/libcxxrt (install) >>> install -C -o root -g wheel -m 444 libcxxrt.a >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/ >>> install -s -o root -g wheel -m 444 libcxxrt.so.1 >>> /usr/local/nanobsd/rr-trunk/obj/_.w/lib/ >>> install -l rs /usr/local/nanobsd/rr-trunk/obj/_.w/lib/libcxxrt.so.1 >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/libcxxrt.so >>> install: symlink ../../lib/libcxxrt.so.1 -> >>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib: File exists >>> *** Error code 71 >>> >>> Stop. >>> >>> I'm not sure what's happening, I already tried reverting locally >>> r301880, thinking it could be related, but this changed nothing. >>> >>> Anyone has some insight? It was working fine up to August 4th. >>> >>> Thanks in advance to anyone giving me some hint! >>> >> >> Is this still reproducible for anyone? I have theories but need it in= >> its broken state to debug it further. >> >=20 > I've created a trivial reproducibility on it and am working on a fix. > So far it appears to be purely an issue in head with dirname(3) compat.= >=20 This is fixed in head r304860 by ed@. It requires updating the host. --=20 Regards, Bryan Drewery --cf7ghGa1b9WxsAbN0XsVw6c6VBTp9MCcE-- --x87c541BtgFlICpFhANrGvIDf8QqPVdsw 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 iQEcBAEBAgAGBQJXwKkgAAoJEDXXcbtuRpfPrf0IAKBAGwUyvHetEFZDLbScpKtz z0/t8P/S1IIs54Tx7n4CnI8SBZH3G9BmNfWrwMNuYMmdKv9gdblerYJ9f1Z0SVs7 /QX/BIXVZyQXPAjHNctT5UgT9ZyyTuAG9rPqmpvh6KhopczxeO/MO7FY+Ef5HhEM Ok4VUSnBO2Ya30Flh0Kb2/At+jqBm0hOIDhqa8qrNtiwtFiLtSblVAT1KxF82h79 Nb+SR/xMNoOhesriwZ8RY6gfefFdKMAJVMM/g1mAQWzAWzl7E0TS+qv8AbnZDfK5 Vge+W9P3BnQDKytOxknA2OHS/F4j9pOQem+NkfhbVS88HnbTGX1VGsqi+zhrKhE= =x4yb -----END PGP SIGNATURE----- --x87c541BtgFlICpFhANrGvIDf8QqPVdsw--