From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Haskell dependencies for custom cabal builds Date: Tue, 12 Feb 2019 20:44:42 +0100 Message-ID: <87bm3giyfp.fsf@fastmail.com> References: <87imxqaxic.fsf@ngyro.com> <87r2cd9ekl.fsf@ngyro.com> <6E48CD3A-9511-4855-8C0D-DC7574546939@asu.edu> <878sykg6d7.fsf@ngyro.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gte5B-00046A-BG for guix-devel@gnu.org; Tue, 12 Feb 2019 14:51:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtdz9-0003E2-NU for guix-devel@gnu.org; Tue, 12 Feb 2019 14:44:52 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:49077) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtdz8-0003BF-Qm for guix-devel@gnu.org; Tue, 12 Feb 2019 14:44:51 -0500 In-Reply-To: <878sykg6d7.fsf@ngyro.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Timothy Sample , John Soo Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello! Timothy Sample writes: > Hi John, > > John Soo writes: > >> Hi there, >> >> I did a little digging this morning and it seems like runhaskell is >> probably deprecated in favor of runghc. Do we expect anyone to be >> using hugs or jhc? Runghc also supports ghc flags. I still need to do >> some more research here but the Haskell configure phase deliberately >> unsets GHC_PACKAGE_PATH. I assume it does this because runhaskell >> supports many Haskell compilers. If custom cabal builds are rare, I >> would suspect that non-ghc builds are even rarer. Would it be possible >> to replace runhaskell with runghc? Or parameterize the command? > > I don=E2=80=99t see how this would help. > > From the build system code, > > Cabal errors if GHC_PACKAGE_PATH is set during 'configure', so unset > and restore it. > > The issue that git-annex has is that it wants to use some packages > before calling into Cabal. If =E2=80=9CGHC_PACKAGE_PATH=E2=80=9D is set = properly, it > will find the packages, proceed normally until calling Cabal, and then > error because Cabal doesn=E2=80=99t like =E2=80=9CGHC_PACKAGE_PATH=E2=80= =9D. Cabal wants to > setup the package search path from the command line arguments instead. > On the other hand, if =E2=80=9CGHC_PACKAGE_PATH=E2=80=9D is not set, Caba= l would > theoretically work, but we never get there! The custom =E2=80=9CSetup.hs= =E2=80=9D code > errors out with missing packages before ever calling Cabal. FWIW here is the upstream issue: Note that it was "fixed" briefly by these commits: Unfortunately it was later reverted due to breaking some edge(?) cases, and a Nix-specific workaround that I don't really understand was merged: I wonder if we should try picking the original Cabal fix from ttuegel, maybe as a separate package if it really is a breaking change. Thoughts? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlxjIioACgkQoqBt8qM6 VPr2YAf/Uy7cY/Sh7yxmS46oVGMUqrlfvcSRT2/lYJ5QppH4aPIdg+6YJJAvoQ+n Qjqq2+/p5s1vs60/WQOhDZhafjrA+1sQCf4jv3rz/F5oyUB7uf7wgAM/kSr4TF6F ebnlHsuiIgEf9kaeddSFTYl8ebkZZjl8O+UDnCny8qqXp6A+IDUbV4RQu6o4ATVn cZGrpn5XMTVg/vQIyMV3flg7eqv+eILeuX/ujzpPc1wYkRnNPm3RbIr+fdl7/GPO 6elQUzaaMdSrUDrPex/Nq20wTJpW4a0pwiIKlQAbNrm5qOKV49dsO2YxFkHTAUpH Teot4W9V0/Bm4BYoE6dJ4Fd/694tHA== =WZRc -----END PGP SIGNATURE----- --=-=-=--