[Haskell-cafe] --disable-{executable-}profiling cabal-install-1.22.0.0 with ghc-7.6.3

[Ozgur Akgun]

On 13 January 2015 at 13:20, Johan Tibell <johan.tibell at gmail.com> wrote:

> Already fixed on the 1.22 branch:
> https://github.com/haskell/cabal/issues/2313
>

Great, thanks!

The fix seems to be allowing the use of the old flag
(--disable-executable-profiling).
Using the new flag (--disable-profiling) with an older ghc also apparently
works, but requires Cabal-1.22.0.0 (as well as cabal-install-1.22.0.0)

So I wonder: why doesn't cabal-install-1.22.0.0 require Cabal-1.22.0.0?

Ozgur


>
> On Tue, Jan 13, 2015 at 5:13 AM, Ozgur Akgun <ozgurakgun at gmail.com> wrote:
>
>>
>> On 13 January 2015 at 13:00, Erik Hesselink <hesselink at gmail.com> wrote:
>>
>>> I've had this problem as well. I think the issue is that 'cabal' now
>>> expects '--disable-profiling', but if you have a custom Setup.hs, it
>>> can be compiled with an older version of the Cabal library, and then
>>> it expects '--disable-executable-profiling' again. What is the output
>>> of 'ghc-pkg list Cabal'?
>>>
>>
>> I have 3 versions of Cabal as reported by "ghc-pkg list Cabal".
>> Cabal-1.16.0 in the global package db, Cabal-1.18.1 and Cabal-1.20.0.0 in
>> the user db.
>> Do you think I should be hiding the old ones?
>>
>> Ozgur
>>
>>
>> _______________________________________________
>> Haskell-Cafe mailing list
>> Haskell-Cafe at haskell.org
>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>
>>
>


-- 
Ozgur Akgun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20150113/58fd9eca/attachment.html>