From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc Date: Tue, 26 Jun 2018 11:49:01 +0200 Message-ID: <874lhpzxma.fsf@fastmail.com> References: <871scu5vle.fsf@netris.org> <87bmbyzbiu.fsf@fastmail.com> <877eml9arq.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXkbu-00075p-Kq for bug-guix@gnu.org; Tue, 26 Jun 2018 05:50:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fXkbq-0005Kx-Mm for bug-guix@gnu.org; Tue, 26 Jun 2018 05:50:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:55983) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fXkbq-0005KL-FD for bug-guix@gnu.org; Tue, 26 Jun 2018 05:50:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fXkbq-0008GK-7J for bug-guix@gnu.org; Tue, 26 Jun 2018 05:50:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877eml9arq.fsf@netris.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 31971@debbugs.gnu.org --=-=-= Content-Type: text/plain Mark H Weaver writes: > Hi Marius, > > Marius Bakke writes: > >> Mark H Weaver writes: >> >>> 'meson-build-system' includes 'patchelf' as an implicit input for all >>> packages that use it, and uses it from its 'fix-runpath' phase, >>> sometimes directly and sometimes via (guix build rpath). >>> >>> 'patchelf' is a nasty hack which seems to only work on Intel-based >>> systems. It certainly doesn't work on 'mips64el-linux', and when I last >>> investigated it seemed hard to fix this. As far as I can tell, it has >>> never built successfully on 'armhf-linux' either: >>> >>> https://hydra.gnu.org/job/gnu/master/patchelf-0.8.armhf-linux/all >>> >>> I don't know about 'aarch64-linux'. >>> >>> Given that 'meson-build-system' is seeing increased usage in some >>> important packages, e.g. 'libinput' and several GNOME packages, this is >>> becoming an increasingly serious problem for non-Intel platforms. >> >> Note that this is already fixed on 'core-updates', with commits >> 3cc9a8a13..800564020. See . > > I believe you're mistaken. Those commits eliminated one of the uses of > 'patchelf' in meson-build-system, but there still remains a call to > 'augment-rpath' which uses patchelf, and patchelf is still added as an > implicit input. Ah yes, you are right. Apoligies for the noise. Since I'm here, I'd like to point out that there has been some activity upstream recently around RPATH handling: https://github.com/mesonbuild/meson/commit/e3757e3d3cf24327c89dd3fc40f6cc933510f676 I believe this commit eliminates the need for "shrink-rpath", and facilities are planned to also control the installed RUNPATH. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlsyDA0ACgkQoqBt8qM6 VPog0Af+JsSYD/oyB81y46t84YkDMXx1hRmUmmgLOxbbnvR8yT9gw8VxKOVlbdSq XMhWq+SHIQTE+agK2GinuWGwPtUZWgPc8k7YhImAzulFrI3Rw70kDmjtTCKg+avx ykZ7rkR1YD/UGQge0yM0bdJy0yO0AN2h6XSawnjmsRNhdauedooLUTpzQCq51KiX Tg5z1s9HhbH/ZD0JUdEw2UA9NeW6HOM6xYgjlplHgl/VwbacmsENuHc81QFQfmya XHw2ir6PHM25Sc5o0W3ofXjqQcwZHpN4+PSmHDWUs/0w1cpG3KQzLQGaRL/yVKJz fwyPbwyfGKbqcfYLYUbV38Ix0HNkAw== =j8bJ -----END PGP SIGNATURE----- --=-=-=--