From: Hans Ulli Kroll <linux@ulli-kroll.de>
To: buildroot@buildroot.org
Cc: Hans Ulli Kroll <linux@ulli-kroll.de>
Subject: [Buildroot] [PATCH] package:uclibc-ng:enable gnu hash for non mips platforms
Date: Sun, 8 Sep 2024 10:36:36 +0200 [thread overview]
Message-ID: <20240908083636.6401-1-linux@ulli-kroll.de> (raw)
In toolchain-wrapper.mk we use both sysv and gnu hash style for all
platforms, except MIPS which uses sysv only.
However uClibc-ng has some extra knob to enable gnu hash via Kconfig,
which is set by default off.
This leads to wrong symbol resolving on armv5 and output of devices,
here on Pogoplug 4 detected with lcpci 3.10.
Signed-off-by: Hans Ulli Kroll <linux@ulli-kroll.de>
---
package/uclibc/uclibc.mk | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/package/uclibc/uclibc.mk b/package/uclibc/uclibc.mk
index de834bac4f..f48ebe6a16 100644
--- a/package/uclibc/uclibc.mk
+++ b/package/uclibc/uclibc.mk
@@ -205,6 +205,12 @@ define UCLIBC_X86_TYPE_CONFIG
endef
endif
+ifneq ($(UCLIBC_TARGET_ARCH),mips)
+define UCLIBC_LDSO_GNU_HASH_SUPPORT
+ $(call KCONFIG_ENABLE_OPT,LDSO_GNU_HASH_SUPPORT)
+endef
+endif
+
#
# Debug
#
@@ -403,6 +409,7 @@ define UCLIBC_KCONFIG_FIXUP_CMDS
$(UCLIBC_SH_TYPE_CONFIG)
$(UCLIBC_SPARC_TYPE_CONFIG)
$(UCLIBC_POWERPC_TYPE_CONFIG)
+ $(UCLIBC_LDSO_GNU_HASH_SUPPORT)
$(UCLIBC_X86_TYPE_CONFIG)
$(UCLIBC_DEBUG_CONFIG)
$(UCLIBC_ENDIAN_CONFIG)
--
2.46.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-09-08 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 8:36 Hans Ulli Kroll [this message]
2024-10-28 22:01 ` [Buildroot] [PATCH] package:uclibc-ng:enable gnu hash for non mips platforms Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240908083636.6401-1-linux@ulli-kroll.de \
--to=linux@ulli-kroll.de \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox