No I am not Also the reason I put it on GHC is that it might have been a specific issue with GHC (although unlikely) On Fri, May 13, 2011 at 3:36 PM, Magnus Therning wrote:

On Fri, May 13, 2011 at 01:34:13AM +1000, Mathew de Detrich wrote:

...

In case this is an issue with archlinux platform specifically and not GHC in general

http://hackage.haskell.org/trac/ghc/ticket/5193

Are you compiling leksah with profiling? If so, try turning it off.

I'm also confused why you raised the bug on GHC's trac, are you not using the Arch package for GHC?

/M

-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. -- Alan Kay

_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell

On Fri, May 13, 2011 at 03:49:55PM +1000, Mathew de Detrich wrote:

Also I am not compiling leksah with profiling, I am just using cabal2arch on the standard leksah package on http://hackage.haskell.org/packages/archive/leksah/0.10.0.4/leksah.cabal

cabal2arch will create a PKGBUILD that supports profiling (you turn it on using an environment variable) and it always turns on building of shared libraries. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

On Fri, May 13, 2011 at 04:08:49PM +1000, Mathew de Detrich wrote:

Well I didn't explicitly turn on profiling as an environment variable, but in any case filepath ships with GHC so that wouldn't fix anything (unless you wanted to use cabal2arch on filepath and have to rebuild the cache for GHC)

I may have been unclear (forgive me if I'm mistaken in believing I haven't quite gotten my point across). Here's the situation as I see it: • GHC ships with static libs, shared libs, and static libs for profiling (it's missing shared libs for profiling) • cabal2arch generates a PKGBUILD that compiles static libs, shared libs and static libs for profiling • Leksah turns on profiling when compiling shared libs What you need to do is modify Leksah's cabal such that it *doesn't* turn on profiling when compiling the shared libs. /M

On Fri, May 13, 2011 at 4:07 PM, Magnus Therning wrote:

...

On Fri, May 13, 2011 at 03:49:55PM +1000, Mathew de Detrich wrote:

...

Also I am not compiling leksah with profiling, I am just using cabal2arch on the standard leksah package on http://hackage.haskell.org/packages/archive/leksah/0.10.0.4/leksah.cabal

cabal2arch will create a PKGBUILD that supports profiling (you turn it on using an environment variable) and it always turns on building of shared libraries.

/M

-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

On Fri, May 13, 2011 at 04:16:39PM +1000, Mathew de Detrich wrote:

Oh no, I understood that perfectly. Technically speaking its an issue with the cabal package file, although I have no idea if this is something cabal package maintainers should be responsible for or if this is a side effect of PKGBUILD supporting profiling

Ah, good, English isn't my native tongue so I'm aware I sometimes express myself clumsily. <rant> IMNSHO the Leksah Cabal file clearly is the culprit here. I personally think that Cabal files uploaded to Hackage shouldn't turn on anything like profiling, shared libs etc. They should configure the bare minimum. It should be left to packagers (e.g. ArchHaskell) to turn on stuff like profiling and shared libs if that's suitable. </rant> /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

On Fri, 2011-05-13 at 07:49 +0100, Magnus Therning wrote:

On Fri, May 13, 2011 at 04:16:39PM +1000, Mathew de Detrich wrote:

...

Oh no, I understood that perfectly. Technically speaking its an issue with the cabal package file, although I have no idea if this is something cabal package maintainers should be responsible for or if this is a side effect of PKGBUILD supporting profiling

Ah, good, English isn't my native tongue so I'm aware I sometimes express myself clumsily.

<rant> IMNSHO the Leksah Cabal file clearly is the culprit here. I personally think that Cabal files uploaded to Hackage shouldn't turn on anything like profiling, shared libs etc. They should configure the bare minimum. It should be left to packagers (e.g. ArchHaskell) to turn on stuff like profiling and shared libs if that's suitable. </rant>

/M

On this note, when removing the profiling options, the leksah package still fails to build due to this error http://hackage.haskell.org/trac/hackage/ticket/656. It probably has something to do with the fact that I had to install haddock through cabal2arch to build leksah (and its components) in the first place due to GHC only providing a haskell binary (and there being no haddock package on AUR) Im not going to add a comment to the ticket above (yet) because I am not sure if its an issue due to me installing haddock as I have done

On Fri, 2011-05-13 at 08:45 +0100, Magnus Therning wrote:

On Sat, May 14, 2011 at 08:35, Mathew de Detrich wrote:

...

On Fri, 2011-05-13 at 07:49 +0100, Magnus Therning wrote:

...

On Fri, May 13, 2011 at 04:16:39PM +1000, Mathew de Detrich wrote:

...

Oh no, I understood that perfectly. Technically speaking its an issue with the cabal package file, although I have no idea if this is something cabal package maintainers should be responsible for or if this is a side effect of PKGBUILD supporting profiling

Ah, good, English isn't my native tongue so I'm aware I sometimes express myself clumsily.

<rant> IMNSHO the Leksah Cabal file clearly is the culprit here. I personally think that Cabal files uploaded to Hackage shouldn't turn on anything like profiling, shared libs etc. They should configure the bare minimum. It should be left to packagers (e.g. ArchHaskell) to turn on stuff like profiling and shared libs if that's suitable. </rant>

/M

On this note, when removing the profiling options, the leksah package still fails to build due to this error http://hackage.haskell.org/trac/hackage/ticket/656. It probably has something to do with the fact that I had to install haddock through cabal2arch to build leksah (and its components) in the first place due to GHC only providing a haskell binary (and there being no haddock package on AUR)

Im not going to add a comment to the ticket above (yet) because I am not sure if its an issue due to me installing haddock as I have done

Fair enough. You may also be interested in this Arch bug on GHC: https://bugs.archlinux.org/task/17875

/M

Yup, I am already aware of that. If fixing that bug resolves this issue, then thats great. Just notifying you incase its something else