GCC cannot be cross-compiled to armv5tel

[planetbrian]

Is this a new report?

Yes

System Info

Void 6.12.63_1 x86_64 GenuineIntel uptodate r

Package(s) Affected

gcc-14.2.1+20250405_4

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

Proper build without issues. GCC cross-compiles to armv5tel-musl without issue, but musl1.1 not optimal for me.

Actual behaviour

After completing the pre-build hooks, the gcc build fails during the do_build stage, noting

configure: error: in '/builddir/gcc-14.2.1+20250405/build/fixincludes':
configure: error: C preprocessor "arm-linux-gnueabi-cpp" fails sanity check

Steps to reproduce

1. clone this repo
2. run ./xbps-src binary-bootstrap
3. run ./xbps-src -a armv5tel pkg gcc
4. fails during configure stage

[itscool900]

That command gave me ERROR: failed to create metadir: /usr/arm-linux-gnueabi/var/db/xbps: Permission denied--anyone know a solution?

[mvf]

Confirmed. Configuration fails because linux/limits.h is not found. Not sure if it's the right fix, but this change produced an .xbps for me:

--- a/srcpkgs/gcc/template
+++ b/srcpkgs/gcc/template
@@ -52,7 +52,7 @@ else
 	# when zlib has been compiled with glibc 2.32.
 	LDFLAGS="-lzstd -pthread"
 fi
-makedepends="zlib-devel libzstd-devel"
+makedepends="zlib-devel libzstd-devel kernel-libc-headers"
 depends="binutils libgcc-devel-${version}_${revision}
  libstdc++-devel-${version}_${revision} libatomic-devel-${version}_${revision}"
 checkdepends="dejagnu"

% file gcc
gcc: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux.so.3, BuildID[sha1]=9e91d88e36a9f16679311e659723188bb85759ec, for GNU/Linux 3.2.0, stripped

[oreo639]

Not sure if it's the right fix, but this change produced an .xbps for me:

/usr/arm-linux-gnueabi/include/linux is a part of cross-arm-linux-gnueabi-libc. By manually specifying kernel-libc-headers, those files get overwritten and then deleted when kernel-libc-headers is uninstalled at the end of the built, which is what is happening here since glibc has kernel-libc-headers as a makedep. If you recreate the masterdir after armv5tel glibc is built, then it works.

[planetbrian]

oreo639 and mvf, thank you for your insights. Unfortunately, I am still a bit lost. Should I:

1. do steps 2 and 3 specified above until gcc fails, remake the masterdir, then run steps 2 and 3 again, or...
2. edit srcpkgs/gcc/template in advance to include kernel-libc-headers, then run step 3
3. another option

Does cross-compiling gcc for other architectures enounter the same issue? any fix would be greatly appreciated, thank you!

[oreo639]

Yes, you should remake the masterdir and run steps 2 and 3 again.
The makedepends should be made conditional on not cross compiling: https://github.com/void-linux/void-packages/blob/master/srcpkgs/glibc/template#L55 although ideally the cross build system should probably be redesigned to avoid this issue.