Bug 8506 - Can not build armhf rpms on Fedora 41
Summary: Can not build armhf rpms on Fedora 41
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Build system (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-04 12:46 CET by Alexander Zeijlon
Modified: 2025-02-04 13:33 CET (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Alexander Zeijlon cendio 2025-02-04 12:46:13 CET
I encountered an issue when building cenbuild packages on my Fedora 41 machine, where it fails to strip binaries of debug symbols when building for our armhf-arch.
Comment 1 Alexander Zeijlon cendio 2025-02-04 12:53:47 CET
There is a stage of the rpmbuild proceedure where it calls the script "find-debuginfo" (part of the package debugedit-5.1-4.fc41.x86_64).

This script in turn calls "gdb-add-index" (part of gdb-headless-15.2-4.fc41.x86_64), which tries to extract symbols with the command "objcopy" (part of binutils-2.43.1-5.fc41.x86_64).

Apparently objcopy is supposed to be able to guess the file format of the input file, but I instead get this error from find-debuginfo:

> /usr/bin/find-debuginfo -j8 --strict-build-id -m -i --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 <path to build folder>
> find-debuginfo: starting
> Extracting debug info from 1 files
> objcopy: Unable to recognise the format of the input file `<path to build folder>/BUILDROOT/opt/cendio-build/arch/armhf/usr/arm-none-linux-gnueabi/sys-root/usr/lib/libXau.so.6.0.0'
> *** ERROR:: GDB exited with exit status 1 during index generation
Comment 2 Alexander Zeijlon cendio 2025-02-04 12:59:38 CET
It is possible to read out the file format of the file in question with "objdump -f <file>".

If I make local copies of find-debuginfo, gdb-add-index, and edit the call to objcopy to explicitly provide the file format that I got from objdumb with "--input-target=elf32-little", the script runs successfully.

Note that this was run outside the rpmbuild context.

Note You need to log in before you can comment on or make changes to this bug.