Hello Erik,

> On 13 Oct 2025, at 16:48, ummeegge <[email protected]> wrote:
> 
> 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.

Yes, those are packages that you will need.

> 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?

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 —-target=aarch64 gettoolchain
  ./make.sh —-target=aarch64 clean

And then restart the build as usual with:

  ./make.sh —-target=aarch64 build

> Any hints or suggestions would be greatly appreciated.
> 
> Best
> 
> Erik
> 


Reply via email to