From: Timothy Sample <samplet@ngyro.com>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36692-done@debbugs.gnu.org
Subject: bug#36692: [PATCH (unified, replaces previous patches)] gnu: Add GHC 8.6.5
Date: Thu, 08 Aug 2019 00:26:39 -0400 [thread overview]
Message-ID: <87r25wnuyo.fsf@ngyro.com> (raw)
In-Reply-To: <20190716194740.23243-1-rob@vllmrt.net> (Robert Vollmert's message of "Tue, 16 Jul 2019 21:47:41 +0200")
Hi Robert,
Robert Vollmert <rob@vllmrt.net> writes:
> This is exactly like GHC 8.4, except for:
> - the sources
> - depends on ghc-8.4 as ghc-bootstrap, since it has a
> minimum requirement of GHC 8.2 as a bootstrap compiler
> - explicitly skip two failing tests
I simplified the package by reusing the inputs and arguments from
“ghc-8.4”. I also made changing “ghc-8” its own commit.
Pushed as a62ddb748f–cce84c34cd. Thanks!
> (Apparently, those tests also fail on older versions, but
> for unclear reasons the packages still build successfully.)
It would be nice if we could make the old versions fail and fix or
disable the failing tests.
-- Tim
prev parent reply other threads:[~2019-08-08 4:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 15:47 [bug#36692] [PATCH 0/2] Add GHC 8.6.5 Robert Vollmert
2019-07-16 15:48 ` [bug#36692] [PATCH 1/2] gnu: Rename ghc-8 to ghc-8.4 Robert Vollmert
2019-07-16 15:48 ` [bug#36692] [PATCH 2/2] gnu: Add GHC 8.6.5 Robert Vollmert
2019-07-16 16:00 ` [bug#36692] test failures Robert Vollmert
2019-07-16 16:28 ` Marius Bakke
2019-07-16 16:36 ` Robert Vollmert
2019-07-16 16:45 ` Marius Bakke
2019-07-16 19:00 ` Robert Vollmert
2019-07-16 18:58 ` [bug#36692] [PATCH 1/2] gnu: ghc@8.6.5: Duplicate build arguments from ghc-8.4 Robert Vollmert
2019-07-16 18:58 ` [bug#36692] [PATCH 2/2] gnu: ghc@8.6.5: Skip failing tests Robert Vollmert
2019-07-16 19:47 ` [bug#36692] [PATCH (unified, replaces previous patches)] gnu: Add GHC 8.6.5 Robert Vollmert
2019-08-08 4:26 ` Timothy Sample [this message]
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=87r25wnuyo.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=36692-done@debbugs.gnu.org \
--cc=rob@vllmrt.net \
/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).