From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc Date: Wed, 27 Jun 2018 22:12:53 +0200 Message-ID: <87fu18xa2i.fsf@gnu.org> References: <871scu5vle.fsf@netris.org> <87bmbyzbiu.fsf@fastmail.com> <877eml9arq.fsf@netris.org> <874lhpzxma.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58923) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fYGpH-0004Lm-E8 for bug-guix@gnu.org; Wed, 27 Jun 2018 16:14:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fYGpG-00051k-Ad for bug-guix@gnu.org; Wed, 27 Jun 2018 16:14:03 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58227) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fYGpG-00051M-6f for bug-guix@gnu.org; Wed, 27 Jun 2018 16:14:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fYGpF-0008M8-UW for bug-guix@gnu.org; Wed, 27 Jun 2018 16:14:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <874lhpzxma.fsf@fastmail.com> (Marius Bakke's message of "Tue, 26 Jun 2018 11:49:01 +0200") 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: Marius Bakke Cc: 31971@debbugs.gnu.org Hello, Marius Bakke skribis: > Mark H Weaver writes: [...] >> 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. Yeah, the reason is that implementing =E2=80=98augment-rpath=E2=80=99 is ob= viously harder than implementing =E2=80=98shrink-rpath=E2=80=99 (the result might n= ot fit.) > 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/e3757e3d3cf24327c89dd3fc40f6cc= 933510f676 > > I believe this commit eliminates the need for "shrink-rpath", and > facilities are planned to also control the installed RUNPATH. I don=E2=80=99t fully understand what this commit does, but it seems to be a step in the right direction. The =E2=80=9CXXX=E2=80=9D found in the RUNPATH of Epiphany () also seem to be there as a way to allow RUNPATH to be adjusted upon install, meaning that we wouldn=E2=80=99t have anything to do on our side. In the meantime, I wonder if we can remove the patchelf dependency selectively for packages where the patchelf phase isn=E2=80=99t necessary. Epiphany may well fall into that category. Thoughts? Ludo=E2=80=99.