Installing binary tarball fails on Linux

[Simon Marlow]

On 08/10/2012 12:57, Joachim Breitner wrote:
> Hi,
>
> Am Montag, den 08.10.2012, 12:08 +0100 schrieb Simon Marlow:
>> On 01/10/2012 13:00, Ganesh Sittampalam wrote:
>>> On 01/10/2012 12:05, Simon Marlow wrote:
>>>
>>>> This probably means that you have packages installed in your ~/.cabal
>>>> from a 32-bit GHC and you're using a 64-bit one, or vice-versa.  To
>>>> avoid this problem you can configure cabal to put built packages into a
>>>> directory containing the platform name.
>>>
>>> How does one do this? I ran into this problem a while ago and couldn't
>>> figure it out:
>>> http://stackoverflow.com/questions/12393750/how-can-i-configure-cabal-to-use-different-folders-for-32-bit-and-64-bit-package
>>
>> I do this at work where I share the same home dir between several
>> different machines, and my .cabal/config contains
>>
>> install-dirs user
>>     prefix: /home/simonmar/.cabal
>>     bindir: $prefix/bin/$arch-$os
>>     -- libdir: $prefix/lib
>>     libsubdir: $pkgid/$compiler/$arch-$os
>>     -- libexecdir: $prefix/libexec
>>     -- datadir: $prefix/share
>>     -- datasubdir: $pkgid
>>     -- docdir: $datadir/doc/$pkgid
>>     -- htmldir: $docdir/html
>>     -- haddockdir: $htmldir
>
> any chance of making that the default, at least for libsubdir? I also
> stumble over it when I use a i386 schroot to test stuff.

Head over to https://github.com/haskell/cabal/ and create an issue (or a 
pull request!).

Cheers,
	Simon