From: Timothy Sample <samplet@ngyro.com>
To: John Soo <jsoo1@asu.edu>
Cc: 39309@debbugs.gnu.org
Subject: [bug#39309] [PATCH WIP] gnu: add stack.
Date: Mon, 10 Feb 2020 01:06:57 -0500 [thread overview]
Message-ID: <87k14vou0u.fsf@ngyro.com> (raw)
In-Reply-To: <CAKf5CqXUOyvDgCG8e9oGxhBxwpC-9sKi3y8RJUfgjXi5s+c+1A@mail.gmail.com> (John Soo's message of "Fri, 7 Feb 2020 17:32:54 +0000")
Hi John,
John Soo <jsoo1@asu.edu> writes:
> Just wanted to CC you because this issue is hard to find thanks to my
> mistaken subject line.
This seems to be due to <https://github.com/haskell/hsc2hs/issues/22>.
Briefly, the “hsc2hs” program bundled with GHC 8.6.5 accepts response
files, but then goes ahead and passes arguments directly to GCC. Newer
versions of “hsc2hs” use response files for GCC, which solves the
“Argument list too long” problem.
My first suggestion would be to make a separate package for “hsc2hs”
using the version listed on Stackage (which is 0.68.6). Then, add it as
a native input to the “stack” package and get it to shadow the version
shipped with GHC.
Failing that, we could consider patching our GHC package. It would be
best to avoid that, though! :)
(Also, there’s a duplicate “ghc-hspec-discover” in the patch set. That
is, we already have an “hspec-discover” package.)
-- Tim
next prev parent reply other threads:[~2020-02-10 6:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 14:56 [bug#39309] .[PATCH] WIP gnu: add stack John Soo
2020-01-29 15:17 ` [bug#39309] [PATCH WIP] " John Soo
2020-02-07 17:32 ` John Soo
2020-02-10 6:06 ` Timothy Sample [this message]
2020-02-13 13:52 ` John Soo
2020-02-13 13:59 ` John Soo
2020-02-13 17:36 ` John Soo
2020-02-13 22:59 ` Timothy Sample
2020-02-16 1:56 ` Timothy Sample
2020-02-19 14:56 ` John Soo
2020-02-20 4:55 ` Timothy Sample
2020-02-22 15:34 ` Timothy Sample
2020-03-11 9:17 ` John Soo
2020-03-11 14:18 ` Timothy Sample
2020-03-13 15:05 ` John Soo
2021-01-01 18:04 ` [bug#39309] .[PATCH] WIP " John Soo
2021-01-01 18:18 ` John Soo
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=87k14vou0u.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=39309@debbugs.gnu.org \
--cc=jsoo1@asu.edu \
/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).