On Wed, 2023-02-22 at 22:58 -0800, Khem Raj wrote:
> Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is
> searched before
> DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> DT_RUNPATH, this order ensures that injecting
> malicious shared objects is way harder with DT_RUNPATH.
>
> This is now default on major linux distributions already
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
> meta/recipes-devtools/binutils/binutils.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-devtools/binutils/binutils.inc
> b/meta/recipes-devtools/binutils/binutils.inc
> index b2dbf241df..c69d29448f 100644
> --- a/meta/recipes-devtools/binutils/binutils.inc
> +++ b/meta/recipes-devtools/binutils/binutils.inc
> @@ -96,6 +96,7 @@ EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
> --disable-werror \
> --enable-deterministic-archives \
> --enable-plugins \
> + --enable-new-dtags \
> --disable-gdb \
> --disable-gdbserver \
> --disable-libdecnumber \
FWIW I 100% agree we should look to enable this.
Sadly, doing so exposes a bug where things that should rebuild don't.
That manifests as a failure in the reproducible test builds on the
autobuilder. I suspect a taskhash problem somewhere, maybe hash
equivalence, maybe somewhere else, hard to say without debugging it.
I've been trying to get to this to help. The first issue was to sort
the other gdb issue this appeared to trigger but was in fact unrelated
and an issue from the recent binutils/gdb version upgrade. I've
debugged the initial buildtools tarball bug and re-deployed buildtools
on the infrastructure. That fixed some of the manifestations but not
all, I then debugged the remaining ones, worked out the regression in
upstream gdb and sent a patch yesterday which was merged upstream to
fix it.
I am trying to get to helping with the problem this patch causes but
these things take a ton of time. Whilst I may get paid to work on the
project, I am one person and I'm getting pulled in a ridiculous number
of directions at once.
People should worry this triggers a reproducibility issue, it means
there is a bug somewhere.
I am hoping to get to this and to help try and debug it but the patch
cannot merge until we get to the bottom of the issue it triggers.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178161):
https://lists.openembedded.org/g/openembedded-core/message/178161
Mute This Topic: https://lists.openembedded.org/mt/97178429/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
