From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: help-guix@gnu.org, Adrien 'neox' Bourmault <neox@a-lec.org>,
Jason Self <j@jxself.org>
Subject: Guix 1.4.0+i686: getting ghc substitutes?
Date: Fri, 18 Oct 2024 22:26:05 +0200 [thread overview]
Message-ID: <20241018222605.4a9270e5@primary_laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Hi,
In GNU Boot we use Guix 1.4.0 instead of the latest revision because
we can easily point to the 1.4.0 manual and we don't need to update our
code following Guix changes.
We also use i686 (--system=i686-linux) to enable to build GNU Boot on
all the computers we support.
Until now that worked fine but we then hit an issue that we cannot
solve on our own.
We also want to use Guix 1.4.0 + --system=i686-linux for building our
website as well and this requires pandoc, which in turn requires ghc.
However even if ghc builds fine for i686, it takes a very long time to
build (more than 1 night of compilation on a ThinkPad X200). Building
on a way faster computer (a KGPE-D16) doesn't make things much faster.
Part of the issue is because tests are very long to run, and another
part is that we have ghc -> ghc@8.6 -> ghc@8.4 -> ghc@8.0 -> ghc@7.
Disabling tests makes the build an order of magnitude faster, but we
still have multiple hours just for building ghc, so it's not good
enough just to get pandoc to build a website.
Would it be possible to somehow trigger a build on one of the default
substitute server to fix this issue?
If not we could simply change the Guix revision and somehow publish the
corresponding manual as well, but using a release probably makes
things much easier for contributors. Not using Guix by default for
building the website is also an option.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-10-18 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 20:26 Denis 'GNUtoo' Carikli [this message]
2024-10-24 14:32 ` Guix 1.4.0+i686: getting ghc substitutes? Denis 'GNUtoo' Carikli
2024-10-25 9:17 ` Andreas Enge
2024-10-26 16:33 ` Denis 'GNUtoo' Carikli
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=20241018222605.4a9270e5@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=j@jxself.org \
--cc=neox@a-lec.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.