all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GCC language front-ends
Date: Wed, 4 Jun 2014 23:46:53 +0200	[thread overview]
Message-ID: <20140604214653.GA7612@debian> (raw)
In-Reply-To: <87mwdsl5p2.fsf@gnu.org>

On Wed, Jun 04, 2014 at 11:34:33PM +0200, Ludovic Courtès wrote:
> That would be too big.  Plus, when you say “all”, do you really mean Ada
> and Java for instance?  These make things definitely bigger.

Okay.

> > Also, maybe we could drop one of the three gcc versions.
> The default package does C and C++.  We could imagine another one that
> would in addition to Objective-C and FORTRAN, yes.  That would save
> build time, at the expense of being somewhat confusing to the user IMO.

Sorry, here I meant the version numbers 4.7.3, 4.8.2 and 4.9.0. Maybe we could
drop 4.7.0?

> One of the GCC 4.8.2 is ‘gcc-final’ in base.scm.

So this is the one that is used for compiling all our packages? Could we
then not drop the gcc-4.8.2 from gcc.scm and let the user install gcc-final?
Or otherwise, give it a different NAME?

> > Is there a way of printing not the line 95 in which the base gcc package is
> > defined from which all others inherit, but the line where the actual package
> > is defined?
> Yes, good idea.
> I’ve just committed this patch:

Hm, I meant in all generality for all packages that are inherited. Would
this be easily possible?

Andreas

  reply	other threads:[~2014-06-04 21:47 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 [this message]
2014-06-05 13:00     ` Ludovic Courtès
2014-06-05 15:42       ` Andreas Enge
2014-06-05 16:12         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140604214653.GA7612@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.