From owner-freebsd-arm@freebsd.org Thu Oct 12 13:39:36 2017 Return-Path: Delivered-To: freebsd-arm@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 7AFA0E29EBA for ; Thu, 12 Oct 2017 13:39:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F13B87767C; Thu, 12 Oct 2017 13:39:35 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([141.89.153.2]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MKKaI-1e0zoP3eIY-001kKE; Thu, 12 Oct 2017 15:39:28 +0200 Date: Thu, 12 Oct 2017 15:39:26 +0200 From: "Hartmann, O." To: Ian Lepore Cc: "O. Hartmann" , freebsd-arm@FreeBSD.org Subject: Re: NanoBSD: Current/NANO_ARCH=aarch64: chroot: : No such file or directory Message-ID: <20171012153922.6e747356@hermann> In-Reply-To: <1507762426.8386.24.camel@freebsd.org> References: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> <1507762426.8386.24.camel@freebsd.org> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:dzes6rBgadw8ie6W8GvZPURrm+8Peh8OqeIG9KKnx8L0/q4bxnm HLuxiOf5dQ+UEJm+sR9W4uVdZetvcPQ2X2ar1FbL7E60Y/dxnLg1ViuC+LQTpX9jn3rHClb +shU4wQ5nDUmUg1YKT0e2icth/gjodGTle4EuHIlR7zMZxhJsLKqPfaNnnUcGmGU53jCSho yid4yCskifAb3anATTNWw== X-UI-Out-Filterresults: notjunk:1;V01:K0:8Y9IukyYNk0=:ZDDNW4SwMKTmfWjohqy1iJ J7aS8JzuoQpAbTSBTYeCtQwtNJQXSpjmv5IYKUt60+eEwiWZcIdfPF6lI30cYzztmkLzzDFdT icklWH+vDQWD4OT4VCi9qzmM1X7cHO2Na4hM6l+dgVZuqnOGnQavVi4g2WuuCDPkIFFu18Mpb 4zb8siO0Ns0VEG2uZA+RXlEZF0lrNBlFct6SWJ52pCi9FQ6gOxTEiN+TRdIPG9RL9XlEDCJmV gztJzJJaInOyDYJBLxQ3fJEG/Cq1I9XIUN2vOEWpnKglWNTc7qo/zuwEEgxIqcAF5PZu2d8J7 E4YKkxv6amN3fg5ZZ91M9+WwIFqEnXaqwRP/YTu0IgS6m0pDpWebKoyX3O/DKFaGGg4YzSoo1 y6238XQr8TcW2lRepNY1g0xVTAT7cUU/o3yg8tdwpwb3urFdqT8cc24xXOGpdhdoqWJ1UMpND GZnDGxybvK4EKeiWa46EJA8ttH1N5nzbbia19Iuw3AInSqm48h40HoZ8B7mqta14eVYA6qsRr zUFA6Ig435GzSF2MsSnZKMhDTvCkpGvxQSsPfk12r6kuy/Dy6G4Lbqg0QfIkfI+ZN6jVzuIzK 8qZbtHEsMJ0/JvhrWAiaBb9dRlIPZhYWvyK2NPdd94JDhD4bostuTXbBCcLEtLqvIuhVStgST ihQWE6l1CWGegiPEi2A4mkO3bS4FfgrOX9JRDnw2heC5WZ/RSmEnViRU4WdBp/glDHZHob1Bl UVinG9ohwDviKPKyHsGTyIUabbD39reFhnXCgpZS3d3SuVpPVDLGr065fuX27omXu+mYT19iX mz5+3vlB9DRdESYzHHhki9o3aOyb094tsvEG38uMyXKEjk0QEW5ymhFoeejxjEkvlsAj/iWPj PD2cC4yMGJ/TI0X3n3IsIroGGSR60R+NAvXb0PNMRngk1L7lE91mMG5oYWWtqh X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2017 13:39:36 -0000 On Wed, 11 Oct 2017 16:53:46 -0600 Ian Lepore wrote: > On Wed, 2017-10-11 at 20:47 +0200, O. Hartmann wrote: > > Trying to install a successfully cross compiled FreeBSD > > (TARGET=3Darm64) as NanoBSD. NanoBSD is configure using > > NANO_ARCH=3D"aarch64". > >=20 > > Port emulators/qemu-user-static is installed and loaded: > >=20 > > =A08=A0=A0=A0=A01 0xffffffff8243f000 1564=A0=A0=A0=A0=A0imgact_binmisc.= ko > >=20 > > When installing NanoBSD's world and then running mtree, the nanobsd > > script runs into this error: > >=20 > > /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local > > 283 blocks > > + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ > > -f /home/user/Projects/router/nanobsd/mtree/Files.mtree > > ] > > + CR 'mtree -eiU -p /' > > + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc > > 'mtree -eiU -p /' chroot: : No such file or directory Oops, I confused the output. The correct one is: [ from _.cust.cust_install_files ] ... + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree -eiU -p /' chroot: /bin/sh: No such file or directory The empty '' is due to my (hopeless helpless) attempt to fit-in another variable which was set to an empty string. The error looks to me as chroot does't find the proper shell, /bin/sh, but it has been properly installed: # file _.w/bin/sh _.w/bin/sh: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 12.0 (1200051), FreeBSD-style, stripped # ll _.w/bin/sh 839832 -r-xr-xr-x 1 root wheel uarch 261K 12 Okt. 15:32 _.w/bin/sh NanoBSD works on the native host when building on host arch amd64 for host arch amd64 and I guess it is due to the properly installed OS of the host. I do not get the problem here. qemu_user_static should catch up with the alien binary here - I suppose it does. The absolute path should ensure the use of the right binary ... Regards, Oliver > > =20 >=20 > I'm not sure how or why it's happening (I've never used nanobsd), but > the complaint is about those empty quotes ('') between the pathname > and the /bin/sh in the chroot command. =A0It's trying to run a program > named '' and chroot is complaining that it can't find anything named > that. >=20 > -- Ian >=20 > > Is there anything I miss here with the QEMU emulator catching up? > >=20 > > Thanks in advance, > >=20 > > Oliver > > =20