Skip site navigation (1)Skip section navigation (2)
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>

next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000046c31b05dd7fd9da
Content-Type: text/plain; charset="UTF-8"

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
>

--00000000000046c31b05dd7fd9da
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif;font-size:large"><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 25, 2022=
 at 10:26 PM Patrick M. Hausen &lt;<a href=3D"mailto:pmh@hausen.com">pmh@ha=
usen.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">Hi,<br>
<br>
&gt; Am 25.04.2022 um 21:18 schrieb Brooks Davis &lt;<a href=3D"mailto:broo=
ks@freebsd.org" target=3D"_blank">brooks@freebsd.org</a>&gt;:<br>
&gt; Cross install is not supported.=C2=A0 As you have seen, certain tools =
are<br>
&gt; bootstrapped on the build host and used during the install process.=C2=
=A0 You<br>
&gt; might be able to get away with nuking<br>
&gt; /usr/obj/usr/src/arm64.aarch64/tmp/legacy (or maybe tmp) and then<br>
&gt; 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=3D"font-fami=
ly:tahoma,sans-serif;font-size:large" class=3D"gmail_default">You can cross=
 compile a program and then use it <br></div><div style=3D"font-family:taho=
ma,sans-serif;font-size:large" class=3D"gmail_default">on a related system =
. <br></div><div style=3D"font-family:tahoma,sans-serif;font-size:large" cl=
ass=3D"gmail_default">Please think this is a contribution . In that way , p=
iece by piece</div><div style=3D"font-family:tahoma,sans-serif;font-size:la=
rge" class=3D"gmail_default">you may construct another system .</div><div s=
tyle=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmail_defau=
lt">You are right : Being able to construct an installable system is a</div=
><div style=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmai=
l_default">good idea . When it is not available as a whole , having</div><d=
iv style=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmail_d=
efault">a partial capability is a good step .</div><div style=3D"font-famil=
y:tahoma,sans-serif;font-size:large" class=3D"gmail_default"><br></div><div=
 style=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmail_def=
ault"><br></div><div style=3D"font-family:tahoma,sans-serif;font-size:large=
" class=3D"gmail_default">Mehmet Erol Sanliturk</div><div style=3D"font-fam=
ily:tahoma,sans-serif;font-size:large" class=3D"gmail_default"><br></div><d=
iv style=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmail_d=
efault"><br></div><div style=3D"font-family:tahoma,sans-serif;font-size:lar=
ge" class=3D"gmail_default"><br></div><div style=3D"font-family:tahoma,sans=
-serif;font-size:large" class=3D"gmail_default"><br></div><div style=3D"fon=
t-family:tahoma,sans-serif;font-size:large" class=3D"gmail_default"></div><=
br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
I tried your suggestion - unfortunately no worky:<br>
<br>
cd /usr/src/tools/build;=C2=A0 make DIRPRFX=3Dtools/build/ DESTDIR=3D/usr/o=
bj/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: Operat=
ion 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 f=
aster.<br>
<br>
Kind regards and thanks,<br>
Patrick<br>
</blockquote></div></div>

--00000000000046c31b05dd7fd9da--



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>