Date: Mon, 25 Apr 2022 22:47:03 +0300 From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> To: "Patrick M. Hausen" <pmh@hausen.com> Cc: Brooks Davis <brooks@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Cross-compile worked, cross-install not so much ... Message-ID: <CAOgwaMvQoxZhRNoko_0B%2B%2B0g%2BnpgT=B_3H-aJqV3gHiGumOf-w@mail.gmail.com> In-Reply-To: <7FA0C88D-4446-47DD-BBC0-3300B26D6A27@hausen.com> References: <3D48BE93-7D42-4AB2-82D4-88BBF4E1FD40@hausen.com> <20220425191823.GA89506@spindle.one-eyed-alien.net> <7FA0C88D-4446-47DD-BBC0-3300B26D6A27@hausen.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Apr 25, 2022 at 10:26 PM Patrick M. Hausen <pmh@hausen.com> wrote: > 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? > > You can cross compile a program and then use it on a related system . Please think this is a contribution . In that way , piece by piece you may construct another system . You are right : Being able to construct an installable system is a good idea . When it is not available as a whole , having a partial capability is a good step . Mehmet Erol Sanliturk > I tried your suggestion - unfortunately no worky: > > cd /usr/src/tools/build; make DIRPRFX=tools/build/ > DESTDIR=/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 > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 25, 2022 at 10:26 PM Patrick M. Hausen <<a href="mailto:pmh@hausen.com">pmh@hausen.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br> <br> > Am 25.04.2022 um 21:18 schrieb Brooks Davis <<a href="mailto:brooks@freebsd.org" target="_blank">brooks@freebsd.org</a>>:<br> > Cross install is not supported. As you have seen, certain tools are<br> > bootstrapped on the build host and used during the install process. You<br> > might be able to get away with nuking<br> > /usr/obj/usr/src/arm64.aarch64/tmp/legacy (or maybe tmp) and then<br> > running `make toolchain` to build native versions of those tools.<br> <br> that comes as a big surprise and disappointment. What is the point of cross-compiling, then?<br> How to update a small slow embedded platform?<br> <br></blockquote><div><br></div><div><br></div><div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">You can cross compile a program and then use it <br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">on a related system . <br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">Please think this is a contribution . In that way , piece by piece</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">you may construct another system .</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">You are right : Being able to construct an installable system is a</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">good idea . When it is not available as a whole , having</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">a partial capability is a good step .</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default">Mehmet Erol Sanliturk</div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:large" class="gmail_default"></div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> I tried your suggestion - unfortunately no worky:<br> <br> cd /usr/src/tools/build; make DIRPRFX=tools/build/ DESTDIR=/usr/obj/usr/src/arm64.aarch64/tmp/legacy host-symlinks<br> Linking host tools into /usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin<br> cp: chflags: /usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin/basename: Operation not supported<br> *** Error code 1<br> <br> So I will probably need to checkout and compile on the Pi. What are typical<br> build times on a CM3+? Plus I am going to wear down the builtin eMMC much faster.<br> <br> Kind regards and thanks,<br> Patrick<br> </blockquote></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOgwaMvQoxZhRNoko_0B%2B%2B0g%2BnpgT=B_3H-aJqV3gHiGumOf-w>