Re: Is running cross-build on usb drive possible?

Mark Millard via freebsd-arm <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>

On 2021-Apr-3, at 07:37, Andrew Mitchell via freebsd-arm <[email protected]> wrote:

> I am trying to cross-build i386 src to my arm64. Everything seems ok, buildworld is in good progress. 
> I used: make TARGET_ARCH=arm64 buildworld.
> 
> Next step, I'll make install. But I want this cross-built source tree on a USB drive. 
> I'll try: make DESTDIR=/mnt/usb/i386 installworld
> 
> But one question remains:
> Should I specify TARGET=arm64 with make install?
> 
> Any clue?

Normally one does not examine the whole build infrastructure
to determine if a specific item might not be used at some
stage for a specific target. Instead one just supplies the
items for each make command. So, more like:

make DESTDIR=/mnt/usb/i386 TARGET_ARCH=arm64 installworld

I'll note that naming conventions look odd in the above:
Why would /mnt/usb/i386 be the name of a directory that
will contain files for arm64 instead of for i386? The naming
looks likely to be misleading/confusing.

Less of an issue is /mnt/usb : Presuming "mount . . . /mnt"
was used, having a directory called usb inside the file
system mounted is unusual. It would be even more unusual
to have added a usb directory below /mnt and to have used
"mount . . . /mnt/usb". Creating /media/usb and using
"mount . . . /media/usb" would be more like what is
typical. Normally /mnt is an empty directory before (and
after) it is used as a mount point but /media is not
empty because it contains empty directories used as
mount points.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.