December 2014 - cabal-devel

Re: Linker change in GHC 7.8 leads to widespread issues
by Johan Tibell 04 Dec '14

04 Dec '14

I've merged the patches into the 1.20 branch. Look forward to a patch release this weekend. On Thu, Dec 4, 2014 at 1:43 PM, Yitzchak Gale <gale(a)sefer.org> wrote: > Bryan O'Sullivan wrote: > >> 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... > >> I am not sure whether the correct fix is to pepper… > >> packages... with "-fPIC"... or to instead teach Cabal > >> to do this. > > Aha! Thanks for this explanation of what I have been > suffering from. > > Mikhail Glushenkov wrote: > > I've now fixed this issue in Cabal HEAD and also pushed the fix to > > 1.20 and 1.18 branches. 1.20 and 1.18 point releases should be out > > soon. > > Thanks a million for the speedy response to this > serious issue! > > I can't wait for the point releases. I'll go with HEAD on one > of the branches for now. > > -Yitz > _______________________________________________ > ghc-devs mailing list > ghc-devs(a)haskell.org > http://www.haskell.org/mailman/listinfo/ghc-devs >

1 0

Ready to make release candidates for 1.18 and 1.20 bugfix releases
by Johan Tibell 04 Dec '14

04 Dec '14

Hi! I believe I have merged all the fixes people wanted to see in 1.18 and 1.20. Anyone who's interested please double-check that your fixes are in: 1.18: https://github.com/haskell/cabal/compare/cabal-install-v1.18.0.5...1.18 1.20: https://github.com/haskell/cabal/compare/cabal-install-v1.20.0.3...1.20 If everyone are happy with these, I will try to make some releases this weekend. -- Johan

3 4

Re: Linker change in GHC 7.8 leads to widespread issues
by Miëtek Bak 03 Dec '14

03 Dec '14

I agree, and I’m hoping to help improve these matters with my project, Halcyon (https://halcyon.sh/) Halcyon allows all build-time and run-time dependencies of an application to be explicitly declared and installed with a single invocation. This builds on the great work done recently in Cabal to get us `cabal freeze`, and works around many long-standing Cabal issues, such as the inability to automatically install missing build-tools. Halcyon can also be used to restore entire Haskell installations in seconds, and supports GHC versions including 7.8.3, 7.8.2, 7.6.3, 7.6.1, 7.4.2, 7.2.2, and 7.0.4. Hopefully, being able to swap GHC versions in and out, without needing to have them on disk, should help lessen the amount of work needed for comprehensive testing. I am currently putting the final touches on my project before announcement. Please let me know what you think. -- Miëtek On 2014-12-03, at 18:25, Howard B. Golden <howard_b_golden(a)yahoo.com> wrote: > Hi, > > There aren't more complaints because most people haven't tried 7.8 seriously yet. (I didn't notice the problem since I've only been using GHC 7.8 under Windows.) This points out the need for some sort of regular testing of canaries (full systems producing known results) to test the entire toolchain including common libraries (HP, perhaps) and Cabal. > > At the risk of antagonizing the developers again, I will point out that there is a bit of disconnect between GHC developers, Cabal developers, library developers and users (application developers). Without slowing the GHC developers' creativity, there is a need to look at the experience of the application developers. FWIW, my sense is that there is too much turbulence for many potential application developers to adopt Haskell as their production platform unless they have significant in-house resources to deal with the rapid changes. (As as thought experiment, how many changes have to be made to Real World Haskell's programs to get them to run?) > > > Howard > > > > ----- Original Message ----- > From: Simon Marlow <marlowsd(a)gmail.com> > To: Miëtek Bak <mietek(a)bak.io>; Carter Schonwald <carter.schonwald(a)gmail.com> > Cc: "cabal-devel(a)haskell.org" <cabal-devel(a)haskell.org>; "ghc-devs(a)haskell.org" <ghc-devs(a)haskell.org> > Sent: Wednesday, December 3, 2014 4:03 AM > Subject: Re: Linker change in GHC 7.8 leads to widespread issues > > I'm actually rather surprised we got away without doing this up to now. > Why haven't there been more complaints? > > Cheers, > Simon > _______________________________________________ > ghc-devs mailing list > ghc-devs(a)haskell.org > http://www.haskell.org/mailman/listinfo/ghc-devs

1 0