unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, "Sarah Morgensen" <iskarian@mgsn.dev>
Cc: guix-devel@gnu.org
Subject: Re: gcc: build all languages at once?
Date: Thu, 09 Sep 2021 12:14:37 +0200	[thread overview]
Message-ID: <737d4fcf5041c402135fddeb8c335f86142c9185.camel@telenet.be> (raw)
In-Reply-To: <87r1dyzsf7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Ludovic Courtès schreef op wo 08-09-2021 om 23:08 [+0200]:
> > We could also possibly reuse the 'core' parts of GCC between language
> > frontends, saving some space.  (This is what distros seem to do.)
> 
> That’d be ideal, but I’m not sure it’s feasible.  It’s feasible for FHS
> distros that “just” need to shuffle files around in various binary
> packages, but here we’d have to have several outputs or something, and
> most likely they’d refer to one another.

GCC consists of many separate components  (e.g. ‘libada’, ‘libatomic’, ‘libbacktrae’,
‘libgcc’, that each have their own ‘configure.ac’ script called from the ‘main’
configure.ac.   I'd presume it would be possible to ignore the main configure.ac
let all of them be separate packages, without guix having to move files around.

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-09-09 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 17:43 gcc: build all languages at once? Sarah Morgensen
2021-09-08 21:08 ` Ludovic Courtès
2021-09-09 10:14   ` Maxime Devos [this message]
2021-09-10 19:59   ` Sarah Morgensen

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=737d4fcf5041c402135fddeb8c335f86142c9185.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@gnu.org \
    --cc=iskarian@mgsn.dev \
    --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 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).