commit:     c2d46ef2558c4c67d0ba0d7f8c37b7e906f5b678
Author:     Vaibhav Rustagi <vaibhavrustagi <AT> google <DOT> com>
AuthorDate: Wed Jan 26 19:09:15 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jan 28 07:53:25 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2d46ef2

dev-libs/userspace-rcu: Do autoreconf to fix cross-compilation error.

In the install phase, there are certain libraries which are re-linked
using "/usr/lib64". This creates a problem when cross-compilation is
done.

Snippet from logs:

libtool: relink: aarch64-cros-linux-gnu-clang -shared  -fPIC -DPIC
.libs/liburcu_la-urcu.o .libs/liburcu_la-urcu-pointer.o
.libs/liburcu_la-compat_arch.o .libs/liburcu_la-compat_futex.o
-L/build/lakitu-arm64/tmp/portage/dev-libs/userspace-rcu-0.13.0/image/usr/lib64
-L/usr/lib64 -lurcu-common  -pthread -Os -march=armv8-a+crc
-mtune=cortex-a57 -g -Wl,-O2 -Wl,--as-needed -Wl,--gc-sections
-Wl,--icf=all   -pthread -Wl,-soname -Wl,liburcu.so.8 -o
.libs/liburcu.so.8.0.0

Doing `eautoreconf` in `src_prepare` fixes the problem.

Signed-off-by: Vaibhav Rustagi <vaibhavrustagi <AT> google.com>
Closes: https://github.com/gentoo/gentoo/pull/23973
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/userspace-rcu/userspace-rcu-0.13.0.ebuild | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/dev-libs/userspace-rcu/userspace-rcu-0.13.0.ebuild 
b/dev-libs/userspace-rcu/userspace-rcu-0.13.0.ebuild
index 580b14a63699..4ec9c9c340cd 100644
--- a/dev-libs/userspace-rcu/userspace-rcu-0.13.0.ebuild
+++ b/dev-libs/userspace-rcu/userspace-rcu-0.13.0.ebuild
@@ -3,6 +3,8 @@
 
 EAPI=7
 
+inherit autotools
+
 DESCRIPTION="userspace RCU (read-copy-update) library"
 HOMEPAGE="https://liburcu.org/";
 SRC_URI="https://lttng.org/files/urcu/${P}.tar.bz2";
@@ -15,6 +17,12 @@ RESTRICT="!test? ( test )"
 
 DEPEND="test? ( sys-process/time )"
 
+src_prepare() {
+       default
+
+       eautoreconf
+}
+
 src_configure() {
        local myeconfargs=(
                --enable-shared

Reply via email to