unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 31971@debbugs.gnu.org
Subject: bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc
Date: Tue, 26 Jun 2018 05:07:05 -0400	[thread overview]
Message-ID: <877eml9arq.fsf@netris.org> (raw)
In-Reply-To: <87bmbyzbiu.fsf@fastmail.com> (Marius Bakke's message of "Tue, 26 Jun 2018 01:34:01 +0200")

Hi Marius,

Marius Bakke <mbakke@fastmail.com> writes:

> Mark H Weaver <mhw@netris.org> 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 <https://bugs.gnu.org/31208>.

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.

     Thanks,
       Mark

  reply	other threads:[~2018-06-26  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 22:50 bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc Mark H Weaver
2018-06-25 23:34 ` Marius Bakke
2018-06-26  9:07   ` Mark H Weaver [this message]
2018-06-26  9:49     ` Marius Bakke
2018-06-27 20:12       ` Ludovic Courtès
2018-06-29 18:57 ` Mark H Weaver
2019-01-09 20:41 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877eml9arq.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=31971@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).