On 2022-07-27 04:32, Paulo Neves wrote:
I thought of that myself, but did not yet investigate. We have
hardcode_into_libs disabling in 4 "recipes":
git grep hardcode_into_libs -- meta
recipes-devtools/binutils/binutils/0009-Use-libtool-2.4.patch:
hardcode_into_libs=yes
I thought of that myself, but did not yet investigate. We have
hardcode_into_libs disabling in 4 "recipes":
git grep hardcode_into_libs -- meta
recipes-devtools/binutils/binutils/0009-Use-libtool-2.4.patch:
hardcode_into_libs=yes
recipes-devtools/binutils/binutils/0009-Use-libtool-2.4.patch:
On Tue, 2022-07-26 at 22:23 +0200, Paulo Neves wrote:
> Due to hardcoded rpaths tmpdir contamination happened on lame
> executable. This commit hot patches libtool to not hardcode
> the .libs directory in the rpath. This solves [YOCTO #14863]
>
> Signed-off-by: Paulo Neves
> ---
>
Due to hardcoded rpaths tmpdir contamination happened on lame
executable. This commit hot patches libtool to not hardcode
the .libs directory in the rpath. This solves [YOCTO #14863]
Signed-off-by: Paulo Neves
---
meta/recipes-multimedia/lame/lame_3.100.bb | 4
1 file changed, 4
