unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Debugging info unavailability
Date: Tue, 02 May 2017 12:08:34 +0200	[thread overview]
Message-ID: <87d1brk1ul.fsf@gnu.org> (raw)
In-Reply-To: <20170423020206.41aac1a2@scratchpost.org> (Danny Milosavljevic's message of "Sun, 23 Apr 2017 02:02:06 +0200")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> just now I had to debug a doxygen Segmentation Fault.  I tried to install doxygen:debug but that wasn't available.
>
> I think it would be nice if these outputs were available by default (but not installed by default).

Yeah, on of the reasons this is currently opt-in is disk space on hydra,
as noted in the manual (info "(guix) Installing Debugging Files").

There’s also the fact that packages that do not use the GNU build system
will most likely not produce debugging info out of the box, so adding
“debug” automatically may break many packages.

> If we wanted to do that, we could just adapt guix/build-system/cmake.scm, guix/build-system/gnu.scm and guix/build-system/glib-or-gtk.scm outputs default to say '("out" "debug") instead of '("out").

Rather we should change the default value of the ‘outputs’ field of
<package>.

The problem is that we’d have to add a line like:

  (outputs '("out"))

to all the packages that do not provide debugging symbols (such as
Perl/Python/Ruby packages), which could be a lot of them.  Or we could
provide:

  (define-syntax-rule (package/no-debug fields ...)
    (package
      (outputs '("out"))
      fields ...))

Thoughts?

Ludo’.

  parent reply	other threads:[~2017-05-02 10:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23  0:02 Debugging info unavailability Danny Milosavljevic
2017-04-24  7:35 ` Tomas Cech
2017-05-02 10:08 ` Ludovic Courtès [this message]
2017-05-02 16:39   ` Maxim Cournoyer
2017-05-02 21:16     ` Ludovic Courtès
2017-05-03  4:53       ` Maxim Cournoyer
2017-05-03  6:29         ` Ricardo Wurmus
2017-05-03 10:11           ` Ludovic Courtès
2017-05-03 15:22             ` Maxim Cournoyer
2017-05-05 20:31               ` Ludovic Courtès
2017-05-05 21:47                 ` Ricardo Wurmus
2017-05-06 12:21                   ` Ludovic Courtès
2017-05-05 22:09                 ` Maxim Cournoyer
2017-05-06 12:26                   ` Distributing substitutes over GNUnet Ludovic Courtès
2017-05-11 15:05                     ` Maxim Cournoyer
2017-05-06 12:46                   ` Debugging info unavailability ng0
2017-05-11  5:13                     ` Maxim Cournoyer
2017-05-11 16:50                       ` ng0
2017-05-11 21:04                         ` 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=87d1brk1ul.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@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).