From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Cross-compiling for aarch64 and armv6l on x86_64 does not seem to work
Date: Sun, 09 Jan 2022 15:21:31 +0000 [thread overview]
Message-ID: <4D633C0E-93F0-4B47-B02F-C8458FF985F6@ipfire.org> (raw)
In-Reply-To: <3a1ce1fa-59e8-02b0-f37a-073a60b1a67a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]
Hello,
What distribution is this?
> On 9 Jan 2022, at 13:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Michael,
>
> thanks for your reply.
>
>> You will need to have the —-target switch before the command:
>>
>> ./make.sh —-target=aarch64 build
>>
>> Don’t forget to fetch the toolchain first and you might need to install a couple of packages that will emulate this architecture. An error message should let you know if anything is missing.
>
> I did so, installed some missing packages, ran "/usr/sbin/qemu-binfmt-conf.sh", downloaded the toolchain
> for aarch64, and tried to start the build. Sadly, it aborts without any (obvious) error message:
>
> Packaged toolchain compilation
> Checking for necessary space on disk [ DONE ]
> Building LFS
> stage2 [ FAIL ]
>
> Jan 9 13:31:47: Building stage2
>
> ERROR: Building stage2 [ FAIL ]
> Check /home/pmu/devel/IPFire-development/ipfire-2.x/log/_build.base.log for errors if applicable [ FAIL ]
> machine:/home/pmu/devel/IPFire-development/ipfire-2.x # cat /home/pmu/devel/IPFire-development/ipfire-2.x/log/_build.base.log
> Jan 9 13:31:47: Building stage2
>
> That's literally it. Since make.sh does not seem to support a debug/verbose switch, and the output of
> "bash -x ./make.sh --target=aarch64 build" does not gives any helpful information either, I'm afraid I
> have to ask for help again.
Well… where does it stop?
QEMU will definitely complain if something isn’t right. Can you see QEMU being executed at all?
-Michael
>
> In case it helps:
>
> # cat /proc/sys/fs/binfmt_misc/qemu-aarch64
> enabled
> interpreter /usr/bin/qemu-aarch64-binfmt
> flags: P
> offset 0
> magic 7f454c460201010000000000000000000200b700
> mask ffffffffffffff00fffffffffffffffffeffffff
>
> Thanks in advance, and best regards,
> Peter Müller
next prev parent reply other threads:[~2022-01-09 15:21 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 [this message]
2022-01-12 8:09 ` Arne Fitzenreiter
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=4D633C0E-93F0-4B47-B02F-C8458FF985F6@ipfire.org \
--to=michael.tremer@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