From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:54504) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j12El-0001J1-Hx for guix-patches@gnu.org; Mon, 10 Feb 2020 01:08:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j12Ek-0005tZ-Df for guix-patches@gnu.org; Mon, 10 Feb 2020 01:08:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:47610) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j12Ek-0005t0-85 for guix-patches@gnu.org; Mon, 10 Feb 2020 01:08:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j12Ek-0005hc-2s for guix-patches@gnu.org; Mon, 10 Feb 2020 01:08:02 -0500 Subject: [bug#39309] [PATCH WIP] gnu: add stack. Resent-Message-ID: From: Timothy Sample References: Date: Mon, 10 Feb 2020 01:06:57 -0500 In-Reply-To: (John Soo's message of "Fri, 7 Feb 2020 17:32:54 +0000") Message-ID: <87k14vou0u.fsf@ngyro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: John Soo Cc: 39309@debbugs.gnu.org Hi John, John Soo 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 . Briefly, the =E2=80=9Chsc2hs=E2=80=9D program bundled with GHC 8.6.5 accept= s response files, but then goes ahead and passes arguments directly to GCC. Newer versions of =E2=80=9Chsc2hs=E2=80=9D use response files for GCC, which solv= es the =E2=80=9CArgument list too long=E2=80=9D problem. My first suggestion would be to make a separate package for =E2=80=9Chsc2hs= =E2=80=9D using the version listed on Stackage (which is 0.68.6). Then, add it as a native input to the =E2=80=9Cstack=E2=80=9D 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=E2=80=99s a duplicate =E2=80=9Cghc-hspec-discover=E2=80=9D in = the patch set. That is, we already have an =E2=80=9Chspec-discover=E2=80=9D package.) -- Tim