commit:     1dc4c0c194edad65536af4838326f7cb13307523
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Tue May  7 03:15:04 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed May  8 19:19:27 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1dc4c0c1

sys-libs/libseccomp: run elibtoolize in non-live ebuild

When building live, we always run eautoreconf. However, even in release
mode we should still run elibtoolize to get important fixes -- such as
the ones that pass through LTO sanity flags to the link phase.

Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-libs/libseccomp/libseccomp-2.5.5-r1.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/sys-libs/libseccomp/libseccomp-2.5.5-r1.ebuild 
b/sys-libs/libseccomp/libseccomp-2.5.5-r1.ebuild
index 40a0c5635548..153293b5f8ca 100644
--- a/sys-libs/libseccomp/libseccomp-2.5.5-r1.ebuild
+++ b/sys-libs/libseccomp/libseccomp-2.5.5-r1.ebuild
@@ -20,7 +20,7 @@ if [[ ${PV} == *9999 ]] ; then
        inherit autotools git-r3
 else
        AUTOTOOLS_AUTO_DEPEND=no
-       inherit autotools
+       inherit autotools libtool
        
SRC_URI="https://github.com/seccomp/libseccomp/releases/download/v${PV}/${P}.tar.gz
                experimental-loong? ( 
https://github.com/matoro/libseccomp/compare/v${PV}..loongarch-r1.patch
                        -> ${P}-loongarch-r1.patch )"
@@ -78,6 +78,8 @@ src_prepare() {
        if [[ ${PV} == *9999 ]] || use experimental-loong; then
                rm -f "include/seccomp.h" || die
                eautoreconf
+       else
+               elibtoolize
        fi
 }
 

Reply via email to