From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Hans Ulli Kroll <linux@ulli-kroll.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package:uclibc-ng:enable gnu hash for non mips platforms
Date: Mon, 28 Oct 2024 23:01:22 +0100 [thread overview]
Message-ID: <20241028230122.16753363@windsurf> (raw)
In-Reply-To: <20240908083636.6401-1-linux@ulli-kroll.de>
Hello Hans,
Thanks for your patch!
On Sun, 8 Sep 2024 10:36:36 +0200
Hans Ulli Kroll <linux@ulli-kroll.de> wrote:
> In toolchain-wrapper.mk we use both sysv and gnu hash style for all
> platforms, except MIPS which uses sysv only.
The logic in toolchain-wrapper.mk regarding --hash-style is about
building the toolchain-wrapper executable for the host. So I really
don't see how this can be related to the uClibc library built for the
target.
> 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.
In principle, I have nothing against your patch, but I must say I don't
really understand why it solves your problem, and what is the
impact/consequences.
Hans, do you have more details on the problems you are seeing?
Waldemar, any input?
As far as I can see from a quick look, we default to --hash-style=both,
as far as I can see in the Busybox binary:
[ 3] .hash HASH 00000190 000190 000a10 04 A 5 0 4
[ 4] .gnu.hash GNU_HASH 00000ba0 000ba0 000018 04 A 5 0 4
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-28 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 8:36 [Buildroot] [PATCH] package:uclibc-ng:enable gnu hash for non mips platforms Hans Ulli Kroll
2024-10-28 22:01 ` Thomas Petazzoni via buildroot [this message]
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=20241028230122.16753363@windsurf \
--to=buildroot@buildroot.org \
--cc=linux@ulli-kroll.de \
--cc=thomas.petazzoni@bootlin.com \
/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