Build fails with library profiling

[tmcdonell]

@djduke Migrated from #39.

I guess you have enabled library profiling in your $HOME/.cabal/config ?

[tmcdonell]

The ticket you linked (haskell/cabal#2766) seems appropriate, although the problem is present with library profiling enabled. Do we know if that fix is released yet?

> cabal --version
cabal-install version 1.24.0.0
compiled using version 1.24.0.0 of the Cabal library

[djduke]

On 9 Oct 2016, at 08:03, Trevor L. McDonell [email protected] wrote:

@djduke Migrated from #39.

I guess you have enabled library profiling in your $HOME/.cabal/config ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Bingo. I'd forgotten about the user-level config file. Changing the flag to false and the build succeeds.

thanks,
David.

---

David Duke T: +44 113 3436800
Professor of Computer Science E: [email protected]
Head, School of Computing W: www.comp.leeds.ac.uk/scsdjd/
PA: Gaynor Butterwick, E: [email protected] T: +44 113 3435434

[djduke]

The change proposed in haskell/cabal#2766 is in the Cabal 1.24.0.0 release. It may have been in an earlier release; I haven't seen if any subsequent changes also touched profiling/dynamic linking flags.

David.

On 9 Oct 2016, at 08:07, Trevor L. McDonell [email protected] wrote:

The ticket you linked (haskell/cabal#2766) seems appropriate, although the problem is present with library profiling enabled. Do we know if that fix is released yet?

cabal --version
cabal-install version 1.24.0.0
compiled using version 1.24.0.0 of the Cabal library

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[tmcdonell]

hmm, I'll have to take a closer look at that cabal issue, but now that I can at least replicate the problem I'll see if it is possible to work around it. Glad it is building for you again!