unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Peter Mikkelsen <petermikkelsen10@gmail.com>
Cc: 28444-done@debbugs.gnu.org
Subject: [bug#28444] [PATCH 3/3] build-system: Add 'meson-build-system'.
Date: Sun, 17 Sep 2017 15:19:50 +0200	[thread overview]
Message-ID: <87vakhihs9.fsf@gnu.org> (raw)
In-Reply-To: <CADh9keV1P7DdsmEHdG9QgfcDDPJQmTme=iXtnguaLX92S00Xzg@mail.gmail.com> (Peter Mikkelsen's message of "Sat, 16 Sep 2017 19:06:03 +0200")

Hi Peter,

Peter Mikkelsen <petermikkelsen10@gmail.com> skribis:

> and without the shrinking done, the runpath looks like this:
>
> /gnu/store/8y6wd2rfi6p3gpxcz3p1gyzsbxwyc9ha-uuid-cpp-0.6.5.1/lib:$ORIGIN/:/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib:/gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib:/gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib/gcc/x86_64-unknown-linux-gnu/5.4.0/../../..
>
> and with, it looks like this:
>
> /gnu/store/nqdf6kr5cqfqh9z5yprar1yyfqwprj4v-uuid-cpp-0.6.5.1/lib:$ORIGIN/:/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib:/gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib
>
> So the last part of the old runpath is removed, and looking at the
> output of ldd, it seems like it was never needed:
>
> linux-vdso.so.1 (0x00007ffd6cbe2000)
> libuuid.so => /gnu/store/8y6wd2rfi6p3gpxcz3p1gyzsbxwyc9ha-uuid-cpp-0.6.5.1/lib/libuuid.so
> (0x00007feae61bc000)
> libstdc++.so.6 =>
> /gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib/libstdc++.so.6
> (0x00007feae5e42000)
> libgcc_s.so.1 =>
> /gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib/libgcc_s.so.1
> (0x00007feae5c2b000)
> libc.so.6 => /gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libc.so.6
> (0x00007feae588c000)
> libm.so.6 => /gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libm.so.6
> (0x00007feae557a000)
> /gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/ld-linux-x86-64.so.2
> (0x00007feae63c4000)
>
> Now, I am not sure it is worth shrinking, but I just think it is a
> little bit strange having unneeded directories in the runpath :)

The last element of the RUNPATH above comes from GCC or so.  I can’t
hurt and you’ll probably find it on all the binaries we build; it’s not
related to Meson, I think.

So if that’s the only reason for ‘patchelf --shrink-runpath’, I would
argue it’s not a valid one.  :-)

> While trying to build a gnome package, I noticed that the runpath was
> huuuge before shrinking, but I don't have that package definition
> anymore :/

Unless you find a more compelling example ;-) as you build packages with
‘meson-build-system’, I’d suggest we eventually revisit this issue and
get rid of ‘fix-runpath’.  That would remove the dependency on PatchELF,
which is sometimes a bit fragile.

How does that sound?

Thanks,
Ludo’.

  reply	other threads:[~2017-09-17 13:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 12:48 [bug#28444] [PATCH 0/3] Add meson-build-system Peter Mikkelsen
2017-09-13 12:50 ` [bug#28444] [PATCH 1/3] gnu: meson: Update to 0.42.0 Peter Mikkelsen
2017-09-13 12:50   ` [bug#28444] [PATCH 2/3] gnu: Add meson-for-build Peter Mikkelsen
2017-09-15 20:57     ` Ludovic Courtès
2017-09-15 21:00       ` Peter Mikkelsen
2017-09-13 12:50   ` [bug#28444] [PATCH 3/3] build-system: Add 'meson-build-system' Peter Mikkelsen
2017-09-15 21:07     ` Ludovic Courtès
2017-09-16 11:08       ` Peter Mikkelsen
2017-09-16 16:11         ` bug#28444: " Ludovic Courtès
2017-09-16 17:06           ` [bug#28444] " Peter Mikkelsen
2017-09-17 13:19             ` Ludovic Courtès [this message]
2017-09-17 13:24               ` Peter Mikkelsen
2017-09-17 14:01               ` Peter Mikkelsen
2017-09-17 19:21                 ` Ludovic Courtès
2017-09-15 20:53   ` [bug#28444] [PATCH 1/3] gnu: meson: Update to 0.42.0 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=87vakhihs9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28444-done@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).