Chris Marusich skribis:
> Ricardo Wurmus writes:
>
>> Since the GCC build procedure is performed at least two
>> times (once with the bootstrap compiler, and then again with the GCC
>> variant this produces), the resulting GCC binaries should be identical.
>>
>> Except that they are not. One of
Jan Nieuwenhuizen writes:
>>> Usage: guix build gcc-dcc
>>>
>>> Building gcc-dcc tests the diverse double compilation property
>>> of the gcc that Guix is using.
>>>
>>> * gnu/packages/bootstrappable.scm: New file.
>>> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
>>
>> Awesome! Does it build fine
Ricardo Wurmus writes:
> Since the GCC build procedure is performed at least two
> times (once with the bootstrap compiler, and then again with the GCC
> variant this produces), the resulting GCC binaries should be identical.
>
> Except that they are not. One of the reasons is that the binaries
Ludovic Courtès writes:
>> Usage: guix build gcc-dcc
>>
>> Building gcc-dcc tests the diverse double compilation property
>> of the gcc that Guix is using.
>>
>> * gnu/packages/bootstrappable.scm: New file.
>> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
>
> Awesome! Does it build fine out-of-the
Hello!
Ricardo Wurmus skribis:
> When building packages, Guix embeds the absolute file name of the output
> directory in the resulting binary. That’s usually fine and what we
> want.
>
> Now let’s assume that we’d like to build the GCC sources with diverse
> double compilation: we’d have a “gcc
Jan Nieuwenhuizen skribis:
> From c91609e847066c384826d726033146e08d8185ed Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen
> Date: Thu, 2 Nov 2017 06:52:46 +0100
> Subject: [PATCH] gnu: Add clang-gcc, gcc-ddc. WIP
>
> Usage: guix build gcc-dcc
>
> Building gcc-dcc tests the diverse double co
Hi Guix,
hi bootstrappers!
When building packages, Guix embeds the absolute file name of the output
directory in the resulting binary. That’s usually fine and what we
want.
Now let’s assume that we’d like to build the GCC sources with diverse
double compilation: we’d have a “gcc” package that’s
[resending to guix-devel@gnu.org because of mail problems / delays]
Hi Guix,
hi bootstrappers!
When building packages, Guix embeds the absolute file name of the output
directory in the resulting binary. That’s usually fine and what we
want.
Now let’s assume that we’d like to build the GCC sourc
Ricardo Wurmus writes:
> When building packages, Guix embeds the absolute file name of the output
> directory in the resulting binary. That’s usually fine and what we
> want.
>
> Now let’s assume that we’d like to build the GCC sources with diverse
> double compilation: we’d have a “gcc” package
