From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Cross-compiling for aarch64 and armv6l on x86_64 does not seem to work
Date: Wed, 12 Jan 2022 09:09:02 +0100 [thread overview]
Message-ID: <43fa6056742070371a6be711e12089be@ipfire.org> (raw)
In-Reply-To: <76779f22-e5d7-e9aa-edc2-f0b9b53932a5@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Hello Peter,
target must be the first parameter.
./make.sh --target=aarch64 gettoolchain
./make.sh --target=aarch64 downloadsrc
./make.sh --target=aarch64 build
should work but i have not used this since ages because it is
sloooow. I think it is better Micheal creates a vm on the mustang for
this.
Arne
Am 2022-01-08 15:05, schrieb Peter Müller:
> Hello *,
>
> currently having a bunch of kernel-related changes in the queue, I
> need to update the
> kernel configuration files and LFS rootfiles on all architectures we
> support. Only
> having an x86_64 system at hand, I thought "./make.sh shell
> --target=aarch64" would do
> the trick (qemu is installed), but apparently isn't:
>
> # ./make.sh build --target=aarch64
> [lots of output logs omitted]
> *** Build finished in 2:11:20
>
>
> [ DONE ]
> # ls
> build ccache doc .gitignore
> ipfire-2.27.2gb-ext4.x86_64-full-core163.img.xz
> ipfire-2.27.x86_64-full-core163.iso langs log make.sh
> src
> cache config .git html
> ipfire-2.27.2gb-ext4.x86_64-full-core163.img.xz.md5
> ipfire-2.27.x86_64-full-core163.iso.md5 lfs .mailmap packages
> tools
>
> If you could give me a hint on what I'm doing wrong, I would be
> frightfully grateful. :-)
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2022-01-12 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 14:05 Peter Müller
2022-01-09 10:04 ` Michael Tremer
2022-01-09 13:36 ` Peter Müller
2022-01-09 15:21 ` Michael Tremer
2022-01-12 8:09 ` Arne Fitzenreiter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43fa6056742070371a6be711e12089be@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox