Date: Sat, 6 Jun 2020 13:22:12 +0200 From: Gordon Bergling <gbergling@gmail.com> To: Mark Murray <markm@FreeBSD.org> Cc: Ian Lepore <ian@FreeBSD.org>, freebsd-hackers@freebsd.org Subject: Re: Cross compile FreeBSD on amd64 for arm64 failes via compile determination error Message-ID: <38CBC7EF-426B-45EE-9506-17B62F1F60FD@gmail.com> In-Reply-To: <B9800A33-0F6C-407B-8F7A-F565945D627D@FreeBSD.org> References: <20200605183002.GA2973@lion.0xfce3.net> <2e91deb9835aaaadd6dceec95395b81f5257f15b.camel@freebsd.org> <B9800A33-0F6C-407B-8F7A-F565945D627D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark, > Am 06.06.2020 um 11:56 schrieb Mark Murray <markm@FreeBSD.org>: >=20 >=20 >> On 6 Jun 2020, at 00:25, Ian Lepore <ian@FreeBSD.org> wrote: >>=20 >> You cannot do that. The installworld process uses a path that points >> into the obj tree that got built (so that new binaries are used to do >> the install work), and those binaries are compiled for the arch that >> did the build. >=20 > That is my experience. >=20 > I used to work around a closely related problem when I built build* on > a fast machine, and did the install* on the slow ones. As I was using > automounts, I ended up with incompatible paths baked into the build, > so I worked around those with symlinks. >=20 > I never tried this with anything other than i386/i386 or amd64/amd64, > so the above is interesting. Could a viable cross-build* be "fixed" by > symlinks, and somehow and easily forcing a cross-build of the = bootstrap > tools? >=20 > My RPis wish to know :-) >=20 > M > =E2=80=94 In theory it should be possible to export the root filesystem of the = RPIs and do a=20 make installworld -DNOROOT DESTDIR=3D/exported/root/rpi-1 or something like this on the fast machine. But for now I have started the build on the raspberry pi directly to = stress test it a bit. :) -- Gordon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38CBC7EF-426B-45EE-9506-17B62F1F60FD>