From: "Ludovic Courtès" <ludo@gnu.org>
To: elaexuotee@wilsonb.com
Cc: guix-devel@gnu.org, mhw@netris.org
Subject: Re: Bug in strip phase of gnu-build-system?
Date: Mon, 04 Jul 2022 15:18:57 +0200 [thread overview]
Message-ID: <87r131auda.fsf@gnu.org> (raw)
In-Reply-To: <2VI4GBZMQD9RW.2FY92Z2FZID5O@"@WILSONB.COM> (elaexuotee@wilsonb.com's message of "Sun, 03 Jul 2022 14:17:20 +0900")
Hi,
elaexuotee@wilsonb.com skribis:
> When `strip-binaries?` is `#f` and a "debug" output is defined, said output
> remains empty. Instead, I expect "debug" to get populated with separated debug
> files.
Hmm I see. The logic was different: #:strip-binaries? #f disables
stripping, but it doesn’t populate the “debug” output either.
If you want to populate the “debug” output, you need to declare a
“debug” output in the package and keep #:strip-binaries? #t.
(I can see arguments for and against both interpretations, but that’s
how it is currently.)
[...]
> If the above is correct, then would it make sense for --with-debug-info to also
> inject a "debug" output as needed? It looks like this would be pretty easy
> under guix/transformations.scm:transforma-package-with-debug-info.
‘--with-debug-info’ is meant to be used when you want to keep debug info
(and there’s no “debug” output). It seemed to me there’s no point in
having that debug info separate in that case, especially since you
wouldn’t be able to refer to it.
HTH!
Ludo’.
next prev parent reply other threads:[~2022-07-04 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 5:17 Bug in strip phase of gnu-build-system? elaexuotee
2022-07-03 11:28 ` Mark H Weaver
2022-07-04 11:15 ` elaexuotee
2022-07-04 13:18 ` Ludovic Courtès [this message]
2022-07-04 15:14 ` elaexuotee
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=87r131auda.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).