unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29184-done@debbugs.gnu.org
Subject: bug#29184: binutils 2.29 fails to set RUNPATH in gcc-cross-boot0
Date: Fri, 16 Mar 2018 15:37:30 +0100	[thread overview]
Message-ID: <87muz8axxx.fsf@fastmail.com> (raw)
In-Reply-To: <87fu9q9xu4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> I tried to cherry-pick the binutils 2.29 update
>> (b0a14e5628eb56052f0c3d21a7b5375f5813b01d), but it breaks the
>> 'validate-runpath' phase of gcc-cross-boot0:
>>
>> starting phase `validate-runpath'
>> validating RUNPATH of 8 binaries in "/gnu/store/ybh1ifgzs717mz5dp1pk2nrgakqg1l8x-gcc-cross-boot0-5.5.0/libexec"...
>> /gnu/store/ybh1ifgzs717mz5dp1pk2nrgakqg1l8x-gcc-cross-boot0-5.5.0/libexec/gcc/x86_64-guix-linux-gnu/5.5.0/cc1: error: depends on 'ld-linux-x86-64.so.2', which cannot be found in RUNPATH ()          
>
> Oh, it looks like this new Binutils adds ld-linux.so to NEEDED, which
> was not the case until now.
>
> I’ve looked at NEWS files but I don’t see where this is coming from.

This turned out to be because "--enable-new-dtags" is now a configure
flag which defaults to off.  So the patch to enable it was overridden
later in ldmain.c.  I removed the patch and enabled the configure flag.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-03-16 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 22:07 bug#29184: binutils 2.29 fails to set RUNPATH in gcc-cross-boot0 Marius Bakke
2017-11-07 10:39 ` Ludovic Courtès
2018-03-16 14:37   ` Marius Bakke [this message]
2018-03-17 18:27     ` 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=87muz8axxx.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=29184-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).