unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: reproducible builds and debugging information
Date: Tue, 24 Mar 2015 22:09:50 +0100	[thread overview]
Message-ID: <87zj72xftt.fsf@gnu.org> (raw)
In-Reply-To: <20150322172632.GB3826@venom> ("Tomáš Čech"'s message of "Sun, 22 Mar 2015 18:26:32 +0100")

Tomáš Čech <sleep_walker@gnu.org> skribis:

> As I was tracing curl code, I needed to rebuild the package with
> "-ggdb" in CFLAGS and enable debug among outputs.
>
> The later doesn't change the hash (and the generated code), but the
> first does.

Both approaches change the output hash.  (As soon as a bit changes in
the build process, the output hash changes.)

Adding a “debug” output is nice because we have support to automatically
DTRT (info "(guix) Installing Debugging Files").

> So I'd like to propose to put "-ggdb" to generally applied CFLAGS for
> whole distribution.

Packages that have an autoconf-based build system, and I suppose most
others, are built with -g.  The binaries get stripped by default and
debugging info is lost unless the package has a “debug” output.

Currently a few key packages have that, but most don’t (I think Debian
does something similar, not sure about other distros.)

We could make it opt-out rather than opt-in, but the issue is disk usage
on build machine (including end-user machines.)  See
<http://lists.gnu.org/archive/html/bug-guix/2013-07/msg00015.html>.

Thoughts?

Ludo’.

  reply	other threads:[~2015-03-24 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 17:26 reproducible builds and debugging information Tomáš Čech
2015-03-24 21:09 ` Ludovic Courtès [this message]
2015-03-25  0:33   ` Tomáš Čech
2015-03-26 21:21     ` Ludovic Courtès
2015-03-26 21:51       ` Tomáš Čech
2015-03-27 21:24         ` Ludovic Courtès
2015-03-27 21:55           ` Tomáš Čech
2015-03-28 17:41             ` Ludovic Courtès
2015-03-29 17:24               ` Mark H Weaver
2015-03-30 19:42                 ` 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=87zj72xftt.fsf@gnu.org \
    --to=ludo@gnu.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).