From: ludo@gnu.org (Ludovic Courtès)
To: Peter Mikkelsen <petermikkelsen10@gmail.com>
Cc: 31208@debbugs.gnu.org
Subject: [bug#31208] [PATCH 0/3] Add 'strip-runpath' in (guix build gremlin)
Date: Mon, 07 May 2018 11:32:31 +0200 [thread overview]
Message-ID: <87muxbak0g.fsf@gnu.org> (raw)
In-Reply-To: <876041swff.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 05 May 2018 22:02:28 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Peter Mikkelsen <petermikkelsen10@gmail.com> skribis:
[...]
>> I think I remember something about the meson developers saying that it
>> is no problem, since libnautilus will be installed in a standard
>> location or something,
>> but I really don't remember, sorry..
>
> What Libtool does is that it “relinks” executables upon “make install”
> so that they have the correct RUNPATH.
I found this issue, which mentions the problem:
https://github.com/mesonbuild/meson/issues/2121#issuecomment-377971590
It’s a pity this isn’t properly solved. :-/
Ludo’.
prev parent reply other threads:[~2018-05-07 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 16:38 [bug#31208] [PATCH 0/3] Add 'strip-runpath' in (guix build gremlin) Ludovic Courtès
2018-04-18 16:40 ` [bug#31208] [PATCH 1/3] gremlin: Preserve offset info for dynamic entries Ludovic Courtès
2018-04-18 16:40 ` [bug#31208] [PATCH 2/3] gremlin: Add 'strip-runpath' Ludovic Courtès
2018-04-18 16:40 ` [bug#31208] [PATCH 3/3] build-system/meson: Use 'strip-runpath' instead of PatchELF Ludovic Courtès
2018-05-04 20:52 ` [bug#31208] [PATCH 0/3] Add 'strip-runpath' in (guix build gremlin) Ludovic Courtès
[not found] ` <CADh9keX7zyDOoNFstawVKdinxNOMKfff3jQuZUOvxFDawZP9Hw@mail.gmail.com>
2018-05-05 20:02 ` Ludovic Courtès
2018-05-07 9:24 ` bug#31208: " Ludovic Courtès
2018-05-07 9:32 ` Ludovic Courtès [this message]
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=87muxbak0g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31208@debbugs.gnu.org \
--cc=petermikkelsen10@gmail.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).