From: Ricardo Wurmus <rekado@elephly.net>
To: 53609@debbugs.gnu.org
Subject: [bug#53609] [PATCH 2/2] gnu: Add ghc-4.
Date: Sat, 29 Jan 2022 19:56:39 +0100 [thread overview]
Message-ID: <871r0qfjro.fsf@elephly.net> (raw)
In-Reply-To: <20220128174852.10637-2-rekado@elephly.net>
There had to be a catch, and sure enough: there is one. This ghc-4
package doesn’t include everything it should. The good news is that the
RTS of GHC is included. The bad news is that the standard library
doesn’t exist.
This old build system is a bit too optimistic and will ignore any build
failure. There are two failures:
--8<---------------cut here---------------start------------->8---
make[3]: *** No rule to make target 'Array.o', needed by 'libHSstd.a'. Stop.
[…]
make[2]: *** No rule to make target 'utils/Argv.o', needed by 'hsc'. Stop.
--8<---------------cut here---------------end--------------->8---
“Stop.” here is not to be taken literally, it seems. The build
continues but libHSstd.a doesn’t make it to the finish line. Array.o
would presumably be built from Haskell code.
This means that the vision I had during a fever dream is still worth
following: combine the GHC RTS with the Hugs interpreter to interpret
the Haskell code of GHC 4 to use it to compile the Haskell code of GHC 4.
--
Ricardo
next prev parent reply other threads:[~2022-01-29 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:35 [bug#53609] [PATCH] Add GHC 4 for the Haskell bootstrap Ricardo Wurmus
2022-01-28 17:48 ` [bug#53609] [PATCH 1/2] gnu: Add perl-5.14 Ricardo Wurmus
2022-01-28 17:48 ` [bug#53609] [PATCH 2/2] gnu: Add ghc-4 Ricardo Wurmus
2022-01-29 18:56 ` Ricardo Wurmus [this message]
2022-02-05 0:08 ` [bug#53609] [PATCH v2 1/4] gnu: Add perl-5.14 Ricardo Wurmus
2022-02-05 0:08 ` [bug#53609] [PATCH v2 2/4] gnu: Add gcc-2.95-wrapper Ricardo Wurmus
2022-02-05 0:08 ` [bug#53609] [PATCH v2 3/4] gnu: Add glibc-2.2.5 Ricardo Wurmus
2022-02-05 14:44 ` Maxime Devos
2022-02-05 0:08 ` [bug#53609] [PATCH v2 4/4] gnu: Add ghc-4 Ricardo Wurmus
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=871r0qfjro.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=53609@debbugs.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).