Re: reproducible builds and debugging information

2015-03-30 Thread Ludovic Courtès
Mark H Weaver skribis: > I think what Tomáš suggested above does not conflict with the design of > Nix and Guix. As I understand it, he's suggesting that we have > 'outputs' default to '("out" "debug") but then the debug outputs would > be immediately discarded for most packages. This would sav

Re: reproducible builds and debugging information

2015-03-29 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > Tomáš Čech skribis: > >> On Fri, Mar 27, 2015 at 10:24:22PM +0100, Ludovic Courtès wrote: >>>Tomáš Čech skribis: >>> Imagine situation where you added "debug" output to every package and after each build the newly generated store with debug info

Re: reproducible builds and debugging information

2015-03-28 Thread Ludovic Courtès
Tomáš Čech skribis: > On Fri, Mar 27, 2015 at 10:24:22PM +0100, Ludovic Courtès wrote: >>Tomáš Čech skribis: >> >>> On Thu, Mar 26, 2015 at 10:21:35PM +0100, Ludovic Courtès wrote: >> >>[...] >> > On openSUSE you have available all the subpackage providing stripped > debug informations a

Re: reproducible builds and debugging information

2015-03-27 Thread Tomáš Čech
On Fri, Mar 27, 2015 at 10:24:22PM +0100, Ludovic Courtès wrote: Tomáš Čech skribis: On Thu, Mar 26, 2015 at 10:21:35PM +0100, Ludovic Courtès wrote: [...] On openSUSE you have available all the subpackage providing stripped debug informations and subpackage providing source code from the

Re: reproducible builds and debugging information

2015-03-27 Thread Ludovic Courtès
Tomáš Čech skribis: > On Thu, Mar 26, 2015 at 10:21:35PM +0100, Ludovic Courtès wrote: [...] >>> On openSUSE you have available all the subpackage providing stripped >>> debug informations and subpackage providing source code from the >>> moment of build (so DWARF information in debug part can

Re: reproducible builds and debugging information

2015-03-26 Thread Tomáš Čech
On Thu, Mar 26, 2015 at 10:21:35PM +0100, Ludovic Courtès wrote: Tomáš Čech skribis: On Tue, Mar 24, 2015 at 10:09:50PM +0100, Ludovic Courtès wrote: [...] Packages that have an autoconf-based build system, and I suppose most others, are built with -g. I can't confirm this statement. I

Re: reproducible builds and debugging information

2015-03-26 Thread Ludovic Courtès
Tomáš Čech skribis: > On Tue, Mar 24, 2015 at 10:09:50PM +0100, Ludovic Courtès wrote: [...] >>Packages that have an autoconf-based build system, and I suppose most >>others, are built with -g. > > I can't confirm this statement. > > I added "debug" output to curl package: Indeed, I just check

Re: reproducible builds and debugging information

2015-03-24 Thread Tomáš Čech
On Tue, Mar 24, 2015 at 10:09:50PM +0100, Ludovic Courtès wrote: Tomáš Čech 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 approa

Re: reproducible builds and debugging information

2015-03-24 Thread Ludovic Courtès
Tomáš Čech 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 t

reproducible builds and debugging information

2015-03-22 Thread Tomáš Čech
Hello Guix! I have question about reproducible builds and generating debugging information. 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. So I'd l