From: Julien Lepiller <julien@lepiller.eu>
To: 32894@debbugs.gnu.org
Subject: bug#32894: Exception in validate-runpath phase
Date: Wed, 03 Oct 2018 10:14:21 +0200 [thread overview]
Message-ID: <ee726bc8e7295ec7447baa4fcfd4ab16@lepiller.eu> (raw)
In-Reply-To: <877ej0o7ht.fsf@gnu.org>
Le 2018-10-02 14:31, ludo@gnu.org a écrit :
> Hello Julien,
>
> [...]
>
> Then again, these are “.debuginfo” files so perhaps they are the result
> of home-made ELF stripping (we don’t have this problem with “.debug”
> files created with objcopy & co.).
>
> I can see two short-term “solutions”:
>
> 1. Remove those .debuginfo files prior to the ‘validate-runpath’
> phase.
>
> 2. Set #:validate-runpath? #f.
>
> Could you check in your build logs how those .debuginfo files are
> produced?
>
> HTH!
>
> Ludo’.
As a workaround, I found that passing --with-native-debug-symbols=zipped
to the configure script allowed validate-runpath to complete
successfully. This option is documented as the prefered value for
distributions, so I think it's a good thing to have. I creates zipped
versions of these .debuginfo files, so validate-runpath doesn't look at
them.
There is no mention of debuginfo until the install phase in my build
log, so I don't know how they are built.
next prev parent reply other threads:[~2018-10-03 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 12:53 bug#32894: Exception in validate-runpath phase Julien Lepiller
2018-10-02 12:31 ` Ludovic Courtès
2018-10-03 8:14 ` Julien Lepiller [this message]
2018-10-08 12:21 ` Ludovic Courtès
2021-11-19 14:51 ` Julien Lepiller
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=ee726bc8e7295ec7447baa4fcfd4ab16@lepiller.eu \
--to=julien@lepiller.eu \
--cc=32894@debbugs.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).