unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Olivier Dion via <help-guix@gnu.org>
Subject: Re: Questions regarding substitutes with debug output
Date: Mon, 25 Apr 2022 00:10:01 -0400	[thread overview]
Message-ID: <87fsm13ism.fsf@gmail.com> (raw)
In-Reply-To: <87y1zu8r7q.fsf@laura> (Olivier Dion's message of "Sun, 24 Apr 2022 10:56:57 -0400")

Hi,

Olivier Dion <olivier.dion@polymtl.ca> writes:

> On Sat, 23 Apr 2022, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> When the package uses the gnu-build-system, it is usually just adding a
>> "debug" outputs and the copying of the stripped symbols to this output
>> is taken care of automatically.  Some packages use their own flags or a
>> release build without symbols in which case just adding "debug" alone
>> won't be enough.
>
> Right.  My guess is that project using autotools are handled
> automagically.  Although, I don't know of any configuration option for
> splitting debug symbols from binaries in autotools.

If you are curious, it's defined in the 'strip' phase in (guix build
gnu-build-system).  By default Autoconf causes the builds to include the
debug symbols (-g).  In the usual case (no "debug" output defined on a
Guix package), these debug symbols are simply stripped (using 'strip',
part of GNU binutils) and discarded.  When the "debug" output exists,
the debug symbols are instead copied to the debug output.

It should also work with the other C/C++ build systems such as
meson-build-system or cmake-build-system so long as they generate debug
symbols by default (which they should).

I hope that helps,

Maxim


  reply	other threads:[~2022-04-25  4:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 17:32 Questions regarding substitutes with debug output Olivier Dion via
2022-04-22  4:22 ` Maxim Cournoyer
2022-04-22 14:29   ` Olivier Dion via
2022-04-24  3:38     ` Maxim Cournoyer
2022-04-24 14:56       ` Olivier Dion via
2022-04-25  4:10         ` Maxim Cournoyer [this message]
2022-04-28  8:13     ` zimoun
2022-04-28  8:58       ` Ricardo Wurmus
2022-04-28 14:11       ` Olivier Dion via
2022-04-28 14:18         ` Ricardo Wurmus
2022-04-28 14:25           ` Olivier Dion via
2022-04-29  5:06             ` Ricardo Wurmus
2022-04-28 14:20         ` Olivier Dion via
2022-04-29  8:49         ` zimoun
2022-04-29 14:47           ` Olivier Dion via
2022-04-29 16:01             ` Ricardo Wurmus
2022-04-29 16:17               ` Olivier Dion via
2022-04-29 20:08                 ` Ricardo Wurmus
2022-04-29 20:53                   ` Olivier Dion via
2022-05-09 10:33                   ` zimoun
2022-05-09 13:33                     ` Ricardo Wurmus
2022-05-09 14:37                       ` zimoun
2022-04-29 16:06             ` zimoun

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=87fsm13ism.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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.
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).