Date: Mon, 25 Apr 2022 21:26:04 +0200 From: "Patrick M. Hausen" <pmh@hausen.com> To: Brooks Davis <brooks@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org> Subject: Re: Cross-compile worked, cross-install not so much ... Message-ID: <7FA0C88D-4446-47DD-BBC0-3300B26D6A27@hausen.com> In-Reply-To: <20220425191823.GA89506@spindle.one-eyed-alien.net> References: <3D48BE93-7D42-4AB2-82D4-88BBF4E1FD40@hausen.com> <20220425191823.GA89506@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Am 25.04.2022 um 21:18 schrieb Brooks Davis <brooks@freebsd.org>: > Cross install is not supported. As you have seen, certain tools are > bootstrapped on the build host and used during the install process. = You > might be able to get away with nuking > /usr/obj/usr/src/arm64.aarch64/tmp/legacy (or maybe tmp) and then > running `make toolchain` to build native versions of those tools. that comes as a big surprise and disappointment. What is the point of = cross-compiling, then? How to update a small slow embedded platform? I tried your suggestion - unfortunately no worky: cd /usr/src/tools/build; make DIRPRFX=3Dtools/build/ = DESTDIR=3D/usr/obj/usr/src/arm64.aarch64/tmp/legacy host-symlinks Linking host tools into /usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin cp: chflags: /usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin/basename: = Operation not supported *** Error code 1 So I will probably need to checkout and compile on the Pi. What are = typical build times on a CM3+? Plus I am going to wear down the builtin eMMC = much faster. Kind regards and thanks, Patrick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7FA0C88D-4446-47DD-BBC0-3300B26D6A27>