December 2014 - cabal-devel

making cabal-install into a library?
by Jens Petersen 21 Jan '15

21 Jan '15

Hi, For a while I have been thinking cabal-install should really be a library. Has anyone considered or thought about this? I am wondering how much work it may be? Best wishes, Jens

4 4

Cabal 1.22 RC ready to test
by Johan Tibell 03 Jan '15

03 Jan '15

Hi all, I've now prepared release candidate for Cabal/cabal-install 1.22. Please test them and report bugs here and/or on the bug tracker ( https://github.com/haskell/cabal/issues) To install: cabal install http://johantibell.com/files/Cabal-1.22.0.0-rc.tar.gz http://johantibell.com/files/cabal-install-1.22.0.0-rc.tar.gz Cabal is now such a big project that's used in so many context (e.g. different OSes) that we need your help to help us test, to make sure that new releases work for you. -- Johan

3 5

The bootstrap.sh script has to go
by Johan Tibell 02 Jan '15

02 Jan '15

Hi all, I've spent more time on the bootstrap.sh script than anything else, making it emulate cabal flag resolution for the network-uri split and make it deal with the fact that network-uri makes Haddock choke. this release. That feels like a somewhat wasteful activity and I'm tired of maintain a stinking pile of shell script. Unless someone is willing to rewrite it as a Haskell program (that could be run using runhaskell), I vote we dump it and instead encourage users to bootstrap using e.g. the Haskell Platform. -- Johan

3 4

1.18 and 1.20 patch releases done
by Johan Tibell 30 Dec '14

30 Dec '14

I just pushed Cabal and cabal-install releases on both the 1.18 and 1.20 branches live.

2 6

Upper bound on "time" in Cabal causes build failure
by Toby Goodwin 20 Dec '14

20 Dec '14

Hi cabal developers, Wasn't sure what best to do with this - please let me know if you'd rather I emailed it elsewhere, or opened an issue against the github project, or... I'm trying to build haskell-platform-2014.2 from source, with the latest cabal: cabal-install version 1.20.0.4 using version 1.20.0.3 of the Cabal library The build plan it constructs for the hptool sandbox includes Cabal-1.2.4! (That's not a typo.) The problem seems to be that it chooses time-1.5, and then discovers that all recent versions of Cabal have the constraint "time < 1.5", so digs up this fossil from the attic. So I think there are two problems here. The small and simple one is that we need a release of Cabal with "time < 1.6" - you appear to have this in the master branch already; can it go on the 1.20 branch? Do you want me to create an issue / pull request? The larger problem is that cabal should have found a better build plan. I'm naive about the internals of dependency resolution, but I would have expected it to prefer taking time back 1 release over taking Cabal back 18. It would also be nice if it could have deduced that Cabal-1.2.4 wasn't actually going to build with recent ghc versions. Thanks for your time, Toby.

3 2

Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
by Herbert Valerio Riedel 19 Dec '14

19 Dec '14

Hello Cabal developers! To keep it short: GHC 7.10.1 RC1 is planned for a release shortly before Xmas, and it would be great if there was a Cabal 1.22.x RC to go along with that. Is it possible for you to get Cabal (the library) in such a state by mid-December (i.e. in 2 weeks from now)? Cheers, hvr

4 8

Please test: release candidates for Cabal/cabal-install patch releases on the 1.18 and 1.20 branches
by Johan Tibell 13 Dec '14

13 Dec '14

I've uploaded release candidates for Cabal/cabal-install patch releases on the 1.18 and 1.20 branches: https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-… https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-… Please test, especially if one of your fixes are in this release. You can install both both lib and exe using: cabal install <Cabal URL> <cabal-install URL> Changelogs: Cabal-1.18.1.5: e4660ff17f923e999080e21a20062d0df8d24bb6 The download dir on haskell.org moved fb3db6313b43632fdc9d598140b3eb5a681eb90b Bump Cabal version number to 1.18.1.5 12a698b6db8a2ca55367c54611a269048f4cef7b Build C sources with -fPIC when GHC is using dynamic libraries. cabal-install-1.18.0.6: 79ccaa85bba7957344fb1dca06d84220eff9b73c Bump cabal-install version number to 1.18.0.6 97dc39636bd547782647cb792ceca6c60a7e5ab1 Merge branch '1.18' of https://github.com/snoyberg/cabal into 1.18 4fbb20f52c842a7c7c173555ff7f0c8b5b67dfa1 Support for network-2.6 6f74da062e6d1bdc6db51acd55d0e2676fa56bf2 SavedConfig Monoid instance: make list fields work like Flags. 7380144203a233f81ff67052fc3256cf47b9b71f cabal update: use sandbox config file #1884 Cabal-1.20.0.3 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number to 1.20.0.4 813ce2fc23da81b7bf07418a28258a962c44713e Bump Cabal version number to 1.20.0.3 cee305209129480f28190ee7026076962ba9ca97 The download dir on haskell.org moved b172747adec9ec8d57d8215e9d1cabb448aa6036 Build C sources with -fPIC when GHC is using dynamic libraries. 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert 97c6a72984931f4ccf628736024d3459a033af6c. 343257e96fab526da27d143b653433f45c6c1401 s/2.15/2.14.4/ cabal-install-1.20.0.4 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number to 1.20.0.4 caf257cd96e766b293943bbac07d766ec2f552dd Self-constraint not included in frozen constraints b19175519de6fc40683527c1104ce2a513a03612 Merge branch '1.20' of https://github.com/snoyberg/cabal into 1.20 1c0d8aafbe42921baa56fc36383f34763f69d327 Revert "Remove redundant network constraint" 58517f76cb2ccb33c007da596ede265f1192d3b8 Remove redundant network constraint a747778c25bd339fed9c9a7c77eb3adbf0f162e0 Support for network-2.6 5fcf3d994e5c5a0f101ac04e092a8beedadcdc8d SavedConfig Monoid instance: make list fields work like Flags. 13f9051d34463037569becf6d3f736a8d8a4570e cabal update: use sandbox config file #1884 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert 97c6a72984931f4ccf628736024d3459a033af6c. aa0a6979f3223387aae830cf1d21b2c21978d767 Read installed package info file as UTF-8

5 9

Heads-up: planning to create 1.22 RC on Thursday
by Johan Tibell 13 Dec '14

13 Dec '14

I plan to create the 1.22 RC on Thursday so it can go in the GHC 7.10 RC. That means that most pull requests (especially non-trivial ones) should be merged by then.

2 1

Re: Linker change in GHC 7.8 leads to widespread issues
by Yitzchak Gale 10 Dec '14

10 Dec '14

I wrote: > Aha! Thanks [to Bryan] for this explanation of what I have been > suffering from... > I can't wait for the point releases. I'll go with HEAD on one > of the branches for now. Unfortunately, this patch did *not* fix what I have been suffering from. I'm still getting segfaults. I'll describe what I'm doing. Please let me know if either of the two problems below are actual problems, or if I'm just missing something. I'll submit them as issues if they are problems. Sample code: http://github.com/ygale/test-text-icu The following procedure worked fine for 32 bit Windows versions of GHC previous to 7.8.* and with all recent versions of cabal-install. Using Haskell Platform 2014.2.0.0 (GHC 7.8.3) 64 bit on Windows 7. Using rev. caf257cd96e766b293943bbac07d766ec2f552dd of cabal, the latest rev. at the moment, on the 1.20 branch. I locally changed the version numbers in the cabal files of both Cabal and cabal-install so I could verify that I really am using cabal.exe from that revision. I verified in the source code that the -fPIC fix is included. Clone the above sample code, and unzip ICU4C 54.1 (currently the latest) for 64 bit Windows in a nearby folder. ***Problem #1 (minor): Relative linker paths don't work anymore cabal sandbox init cabal install --extra-lib-dirs=..\relative\path\to\icu\lib64 --extra-include-dirs=..\relative\path\to\icu\include text-icu This fails with: Warning: 'extra-lib-dirs: ../relative/path/to/icu/lib64' directory does not exist. Warning: 'include-dirs: ../relative/path/to/icu/include' directory does not exist. cabal: Missing dependencies on foreign libraries: * Missing C libraries: icuuc, icuin, icudt Note: The same problem occurs if you copy the ICU folders into the source tree. That just gets rid of the warnings that sdist won't work. ***Problem #2 (major): segfault! cabal install --extra-lib-dirs=C:\absolute\path\to\icu\lib64 --extra-include-dirs=C:\absolute\path\to\icu\include text-icu cabal install Now, place .cabal-sandbox\bin\test-text-icu.exe together with the 3 DLLs icudt54.dll, icuin54.dll, and icuuc54.dll from icu\bin64 all together in the same folder. Run test-text-icu. Kaboom! Note: The same problem occurs if you place *all* of the DLLs from icu\bin64 in the folder together with the exe. So it's not a missing DLL. Thanks, Yitz

1 1

Linker change in GHC 7.8 leads to widespread issues
by Bryan O'Sullivan 05 Dec '14

05 Dec '14

Hi folks, It seems that something somewhere in linker-land changed in GHC 7.8 such that packages that include C components now need to be built with position-independent code on some platforms. This affects a number of my packages. I am not sure whether the correct fix is to pepper all of these packages (and presumably dozens to hundreds of other packages on Hackage) with "-fPIC" and issue new releases, or to instead teach Cabal to do this. It would certainly be vastly less disruptive to all of the affected package authors to have Cabal automatically do the right thing here. Could someone who's closer to both piles of code please suggest which approach they believe is more appropriate?

7 11