Linker change in GHC 7.8 leads to widespread issues

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?

whats an example of such a package?
On Tue, Dec 2, 2014 at 4:06 PM, Bryan O'Sullivan
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?
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

On 2014-12-02, at 21:31, Carter Schonwald
whats an example of such a package?
text-icu. https://github.com/bos/text-icu/pull/9 FWIW, I’m in favour of fixing this at the Cabal level. https://github.com/haskell/cabal/issues/2207 -- Miëtek

If someone can figure out what the right fix is and if it happens to be in
Cabal I'd be happy to merge any changes.
On Tue, Dec 2, 2014 at 10:43 PM, Miëtek Bak
On 2014-12-02, at 21:31, Carter Schonwald
wrote: whats an example of such a package?
text-icu. https://github.com/bos/text-icu/pull/9
FWIW, I’m in favour of fixing this at the Cabal level. https://github.com/haskell/cabal/issues/2207
-- Miëtek
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

On 02/12/2014 21:43, Miëtek Bak wrote:
On 2014-12-02, at 21:31, Carter Schonwald
wrote: whats an example of such a package?
text-icu. https://github.com/bos/text-icu/pull/9
FWIW, I’m in favour of fixing this at the Cabal level. https://github.com/haskell/cabal/issues/2207
I'm actually rather surprised we got away without doing this up to now. Why haven't there been more complaints? Cheers, Simon

Hi,
On 2 December 2014 at 22:06, Bryan O'Sullivan
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.
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.

On Wed, Dec 3, 2014 at 12:49 PM, Mikhail Glushenkov < the.dead.shall.rise@gmail.com> 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, Mikhail! Does this imply that package authors can simply advise bug reporters to upgrade cabal-install?

Hi, Am Donnerstag, den 04.12.2014, 01:08 +0100 schrieb Mikhail Glushenkov:
On 4 December 2014 at 00:44, Bryan O'Sullivan
wrote: Thanks, Mikhail! Does this imply that package authors can simply advise bug reporters to upgrade cabal-install?
Yes, once the new point releases of Cabal/cabal-install are out (in a week or two, according to Johan).
is the bug in Cabal or cabal-install? If the former, are we going to include a fixed version of Cabal in GHC-7.8.4? Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org

Hi, Am Donnerstag, den 04.12.2014, 17:44 +0100 schrieb Mikhail Glushenkov:
On 4 December 2014 at 09:45, Joachim Breitner
wrote: is the bug in Cabal or cabal-install?
It's in Cabal. So once the new point releases are out, the users will need to run `cabal install cabal-install --constraint="Cabal > 1.20.0.2"`.
in this case, can we get a fixed Cabal in 7.8.4? Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org
participants (7)
-
Bryan O'Sullivan
-
Carter Schonwald
-
Joachim Breitner
-
Johan Tibell
-
Mikhail Glushenkov
-
Miëtek Bak
-
Simon Marlow