From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: GCC language front-ends
Date: Thu, 05 Jun 2014 18:12:29 +0200 [thread overview]
Message-ID: <87wqcvqqs2.fsf@gnu.org> (raw)
In-Reply-To: <20140605154228.GB16709@debian.eduroam.u-bordeaux.fr> (Andreas Enge's message of "Thu, 5 Jun 2014 17:42:28 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> On Thu, Jun 05, 2014 at 03:00:57PM +0200, Ludovic Courtès wrote:
>> It’s been discussed several times, but there’s no satisfactory solution
>> so far. Changing the name seems like a bad idea, because it’s really
>> gcc. Making either gcc-final or gcc-4.8 private isn’t an option because
>> they’re referred from elsewhere.
>
> Sorry for my forgetfulness. So the references to gcc-4.8 could not be replaced
> by references to gcc-final?
No. It’s a bit tricky but the idea is: gcc-4.8 is the “abstract” recipe
for GCC, whereas gcc-final is a specialized recipe for use in the
bootstrap process.
The abstract recipe has useful properties:
• it is a “normal”, self-contained package recipe, and thus easier to
grasp;
• it can be cross-compiled (whereas gcc-final cannot, because it is
anchored in the bootstrap dependency DAG);
• it can easily be derived (for gfortran, etc.);
• it remains valid even when the default GCC version changes.
So we need that abstract gcc-4.8.
At the same time, for native compilation, we only ever want to use
gcc-final, because gcc-4.8 is just the same compiler built once more
with itself.
So ideally, ‘guix package’ would magically ignore the abstract gcc-4.8
(and coreutils, grep, etc.) and favor their -final variant.
I hope I’m being clear, but I’m not sure. ;-)
Ludo’.
prev parent reply other threads:[~2014-06-05 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 21:22 Hydra time out Andreas Enge
2014-06-04 21:34 ` GCC language front-ends Ludovic Courtès
2014-06-04 21:46 ` Andreas Enge
2014-06-05 13:00 ` Ludovic Courtès
2014-06-05 15:42 ` Andreas Enge
2014-06-05 16:12 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqcvqqs2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.