From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Cross compiling ARM on X86 system
Date: Mon, 13 Oct 2025 17:48:49 +0200 [thread overview]
Message-ID: <544f1c17d5106b4d9388627a7562f00fd112015b.camel@ipfire.org> (raw)
Hi all,
I'm trying to cross-compile IPFire for aarch64 on an HP ProDesk running
Kali Linux. As a first step, I installed qemu-user-static and binfmt-
support to enable ARM binary execution during the build process.
When running sudo ./make.sh --target=aarch64 build, the build proceeds
successfully through stage1 and binutils:
`Full toolchain compilation
stage1
[ 0 ][ DONE ]
binutils (2.45) PASS=1
[ 1:36 ][ DONE ]`
However, it fails during the zlib-ng build with the following error:
`zlib-ng-2.2.5.tar.gz checksum OK
====================================== Installing zlib-ng-2.2.5 ...
# Build the regular version
cd /home/ummeegge/development/dev-aarch/ipfire-
2.x/build_aarch64/usr/src/zlib-ng-2.2.5 && mkdir -pv build
mkdir: created directory 'build'
cd /home/ummeegge/development/dev-aarch/ipfire-
2.x/build_aarch64/usr/src/zlib-ng-2.2.5/build && ../configure \
--prefix=/tools_aarch64
Checking for compiler... cc
Checking for Symbol versioning... Yes.
Compiler error reporting is too harsh for ../configure (perhaps remove
-Werror).
** ../configure aborting.
make: *** [zlib-ng:80: /home/ummeegge/development/dev-aarch/ipfire-
2.x/log_aarch64/zlib-ng-2.2.5-tools] Error 1
make: Leaving directory '/home/ummeegge/development/dev-aarch/ipfire-
2.x/lfs'`
Could this be related to a compatibility issue between the new
toolchain and zlib-ng 2.2.5? Or is it possibly a misconfiguration in
the cross-compilation environment?
Any hints or suggestions would be greatly appreciated.
Best
Erik
next reply other threads:[~2025-10-13 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 15:48 ummeegge [this message]
2025-10-16 16:19 ` Michael Tremer
2025-10-17 9:44 ` ummeegge
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=544f1c17d5106b4d9388627a7562f00fd112015b.camel@ipfire.org \
--to=ummeegge@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