all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Frédéric Mahé" <frederic.mahe@cirad.fr>, 67157@debbugs.gnu.org
Subject: bug#67157: gcc-toolchain@4.8.5 not available on the official substitute servers
Date: Thu, 16 Nov 2023 11:25:18 +0100	[thread overview]
Message-ID: <868r6yvvu9.fsf@gmail.com> (raw)
In-Reply-To: <c2110f92-4338-4562-9c61-414a54547fb8@cirad.fr>

Hi,

Thanks for the report.

On Mon, 13 Nov 2023 at 20:19, Frédéric Mahé <frederic.mahe@cirad.fr> wrote:

> Is the absence of a x86-64 GNU Linux GCC 4.8.5 build deliberate? I can 
> imagine that this old version is not a priority anymore. Nonetheless, it 
> is still very frequent in the wild, at least until the end-of-support of 
> CentOS 7 next year.

No, it is not deliberate, sadly.  Well, I have tried to find a past
revision when gcc-toolchain@4.8.5 builds but I fail.

The Guix Data Service shows that gcc-toolchain@4.8.5 is not available
for the build farm named Bordeaux.  And the substitutes are also missing
on the other build farm named Berlin.

Well, my guess is the issue is related to an update of GCC.  Therefore,
I am trying this commit:

        27322ac30be6816eca33ee946a04d3b0ab32896f
        CommitDate: Thu Sep 8 21:40:00 2022 +0200

which is right before the update to GCC 11 as default.

  guix time-machine --commit=27322ac30be6816eca33ee946a04d3b0ab32896f \
       -- build gcc-toolchain@4.8.5 --no-grafts

Wait and see…

Cheers,
simon




  reply	other threads:[~2023-11-16 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 19:19 bug#67157: gcc-toolchain@4.8.5 not available on the official substitute servers Frédéric Mahé
2023-11-16 10:25 ` Simon Tournier [this message]
2024-01-18 19:39   ` Thomas Schwinge
2024-01-18 20:03     ` Thomas Schwinge

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=868r6yvvu9.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=67157@debbugs.gnu.org \
    --cc=frederic.mahe@cirad.fr \
    /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.