From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4cnY7L0hgxz30Hp for ; Thu, 16 Oct 2025 16:19:26 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4cnY7G5CQ3z2xMF for ; Thu, 16 Oct 2025 16:19:22 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cnY7F5q6nz2W0; Thu, 16 Oct 2025 16:19:21 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1760631562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9nCDJyyBtxHL0Zx6NfLytVnDbfC+7PbHqEPK/d9RVV8=; b=2O/Vj7LAU20o1cwUgmLiandmnAzIoiaRfx5hzb+yTZ6OkUs0HzP1KLiEuLPWH+6qemgsbH a6A9w8YRhFYvxsCQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1760631562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9nCDJyyBtxHL0Zx6NfLytVnDbfC+7PbHqEPK/d9RVV8=; b=a/dM//ZQgWP+xZAAMMm0Iakjd0VRAWPQchnExAt90LaZD4uCDSJCpdmQr2oxW+LCi/8l89 RAAEKFP5O64TgihccxivIk0ynAKcB74p1uRzmI6g/IWbxrCPb4aj4rNxqYfLH8/jUvBF4U 85IrDNH+xPLXUzGr4RvqE19aLoDx+nf1ZcTp9e6JFCrB2KYauxDn4E+QjDOjiAehHxs9un kHQwjzbjhdDDiyM5Uc5aXhBxo5cvGjaTjcBqDVo42VcJH0oY+I6itcW8BToHQ8hlNPoGhR u0Gea8IcT1pVVxMx2llG+dkIEi/w8nyQ9OHNPUEc8J/QrRLo2trpLprALtojzg== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Cross compiling ARM on X86 system From: Michael Tremer In-Reply-To: <544f1c17d5106b4d9388627a7562f00fd112015b.camel@ipfire.org> Date: Thu, 16 Oct 2025 17:19:21 +0100 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <544f1c17d5106b4d9388627a7562f00fd112015b.camel@ipfire.org> To: ummeegge Hello Erik, > On 13 Oct 2025, at 16:48, ummeegge wrote: >=20 > Hi all, >=20 > 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. Yes, those are packages that you will need. > When running sudo ./make.sh --target=3Daarch64 build, the build = proceeds > successfully through stage1 and binutils: >=20 > `Full toolchain compilation > stage1 =20= > [ 0 ][ DONE ] > binutils (2.45) PASS=3D1 = =20 > [ 1:36 ][ DONE ]` >=20 > However, it fails during the zlib-ng build with the following error: >=20 > `zlib-ng-2.2.5.tar.gz checksum OK > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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=3D/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'` >=20 > 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? I would recommend to download the toolchain unless you really have to = re-compile it. Cross-compiling with an emulator is not that easy and I = suppose some extra things (maybe a static version of libc of the host = system) would be required. I suggest to run: ./make.sh =E2=80=94-target=3Daarch64 gettoolchain ./make.sh =E2=80=94-target=3Daarch64 clean And then restart the build as usual with: ./make.sh =E2=80=94-target=3Daarch64 build > Any hints or suggestions would be greatly appreciated. >=20 > Best >=20 > Erik >=20