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 4cp0KX540sz2xXb for ; Fri, 17 Oct 2025 09:44:48 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4cp0KT2PpWz2xJy for ; Fri, 17 Oct 2025 09:44:45 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cp0KS4qjbzTh; Fri, 17 Oct 2025 09:44:44 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1760694284; 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=8/WesFJ6KmePUXv3Wp90+4uB3Ns3GzlEAgXT0OcJy70=; b=vWYqnGR4mCXrQ42hmH4EU7M38OrQEKFcwZU56gSgIgUmO6K8zm/YrK/AyeJHIr3GrnbtGz ttiz7/N8O0MR5pBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1760694284; 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=8/WesFJ6KmePUXv3Wp90+4uB3Ns3GzlEAgXT0OcJy70=; b=L50VEWvKew2CY7lA6Ge3fJsEwpPxT5/bwjaueeNtPyMq60Wd6lvnIRLji5NOVDyCfIu/Dn zMKel0BmNaJ7ERdyiBrQ60qJWYCA4ck407YLMcrFdIOgDQnAYYlH7jz1RxzcX9FKktNGcn RB+LtqerVvOpcmWtbknCfhaOuRkbgewF2SBC0gxC8OjudvNJiNHGRUPPHCV738U5XZqJpM AyYNmb4ZWQVhadEKTXKHLEWPTmh8dQSWbI2cBFur6WEPIP34VnlUdigs/crm8JdSWmQ6ZW cuUYZfVOt92KfUEIE2Cz9ePGFxWWLr6xnkQH5t/+ziZMIbYY8gGopMq/puTtEg== Message-ID: Subject: Re: Cross compiling ARM on X86 system From: ummeegge To: Michael Tremer Cc: development@lists.ipfire.org Date: Fri, 17 Oct 2025 11:44:40 +0200 In-Reply-To: References: <544f1c17d5106b4d9388627a7562f00fd112015b.camel@ipfire.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Hello Michael, thanks for the information. Am using now the precompiled toolchain and it simply works :D . All the best, Erik Am Donnerstag, dem 16.10.2025 um 17:19 +0100 schrieb Michael Tremer: > Hello Erik, >=20 > > 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. >=20 > Yes, those are packages that you will need. >=20 > > When running sudo ./make.sh --target=3Daarch64 build, the build > > proceeds > > successfully through stage1 and binutils: > >=20 > > `Full toolchain compilation > > stage1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 > > =C2=A0=C2=A0=20 > > [=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0 ][ DONE ] > > binutils (2.45) > > PASS=3D1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=20 > > [=C2=A0=C2=A0=C2=A0=C2=A0 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? >=20 > 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. >=20 > I suggest to run: >=20 > =C2=A0 ./make.sh =E2=80=94-target=3Daarch64 gettoolchain > =C2=A0 ./make.sh =E2=80=94-target=3Daarch64 clean >=20 > And then restart the build as usual with: >=20 > =C2=A0 ./make.sh =E2=80=94-target=3Daarch64 build >=20 > > Any hints or suggestions would be greatly appreciated. > >=20 > > Best > >=20 > > Erik > >=20