Source: libgpg-error
Version: 1.43-1
Tags: patch upstream
User: [email protected]
Usertags: rebootstrap
A while ago, libgpg-error gained a feature that enabled configure to
introspect lock objects without running code (via objdump).
Unfortunately, this code is only used for glibc. When cross building for
e.g. musl, it falls back to the old way where you'd have to collect the
results. And since those aren't collected, it fails. The objdump trick
should work on all Linux systems regardless of the C library in used.
That's also what the VoidLinux people think:
https://github.com/void-linux/void-packages/commit/429ac8a534d4e1fffc0c7f5df47a4f4ac67fa2cd
So please consider applying it here as well. I'm attaching the relevant
hunk.
Helmut
--- a/configure.ac
+++ b/configure.ac
@@ -605,7 +605,7 @@
AC_MSG_NOTICE([generated src/lock-obj-pub.native.h for $host])
elif test x$cross_compiling = xyes; then
case $host in
- *-*-linux-gnu*)
+ *-*-linux-*)
AC_CHECK_TOOL(OBJDUMP, [objdump])
if test -n "$OBJDUMP"; then
lock_obj_h_generated=yes
