unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: "37924@debbugs.gnu.org" <37924@debbugs.gnu.org>
Subject: [bug#37924] [PATCH 2/2] ci: Add 'make-gcc-toolchain' packages
Date: Mon, 04 Nov 2019 23:22:04 +0100	[thread overview]
Message-ID: <87sgn34703.fsf@gnu.org> (raw)
In-Reply-To: <rnS1pu4_DHD_IOqgX3DNBHPRyPiBzy6LCTsgOcvZaT4Nkk8N1UfyHAteBHrA5ABj5ZR1K_VzBQy7wL6XAOoQEh27GD8PF37fvjDeD3do9eI=@carldong.me> (Carl Dong's message of "Fri, 25 Oct 2019 16:21:40 +0000")

Hi,

Carl Dong <contact@carldong.me> skribis:

> * gnu/ci.scm (%core-packages): Add 'glibc-2.28', a toolchain with
> default 'gcc', and a toolchain targeting 'glibc-2.28'.

The problem is ‘%core-packages’ is only built when we explicitly choose
the “core” subset in CI (which we do only when experimenting with
‘core-updates’ early on); in other cases, all the public packages get
built and ‘%core-packages’ does not matter.

Would it be an option to have:

  (define-public gcc/glibc-2.28
    (make-gcc-libc gcc glibc-2.28))

in (gnu packages base), or does that create circular dependency issues
(I don’t think so, but better be safe)?

If we did that, that package would automatically picked up in CI.

Thanks,
Ludo’.

  reply	other threads:[~2019-11-04 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 15:40 [bug#37924] [PATCH] gnu: Fix make-gcc-libc Carl Dong
2019-10-25 16:21 ` [bug#37924] [PATCH 2/2] ci: Add 'make-gcc-toolchain' packages Carl Dong
2019-11-04 22:22   ` Ludovic Courtès [this message]
2019-11-04 22:18 ` [bug#37924] [PATCH] gnu: Fix make-gcc-libc Ludovic Courtès
2019-11-16 16:36 ` bug#37924: " 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

  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=87sgn34703.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37924@debbugs.gnu.org \
    --cc=contact@carldong.me \
    /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).