[commit: ghc] master: Tidy up cross-compiling (109a1e5)

Simon Marlow marlowsd at gmail.com
Fri Jan 18 17:27:09 CET 2013


On 18/01/13 16:17, Stephen Paul Weber wrote:
> Somebody claiming to be Simon Marlow wrote:
>> On 18/01/13 15:25, Stephen Paul Weber wrote:
>>> Somebody claiming to be Simon Marlow wrote:
>> Right, I didn't know that autoconf would automatically look for the
>> tools as <platform>-tool.  I'll update the docs.
>
> Cool.  Looks good.
>
>>> cabal --with-ghc=<cross-ghc> --with-ld=<ld> ...
>>>
>> Ah, in my case the GHC I built was called ghc-7.7.20130116, so it
>> didn't clash with anything else in .cabal.  You could also configure
>> your cabal to put the arch/os in the directory name.
>
> ~/.cabal/bin ?

I'm thinking mainly about libraries here, yes if you want to build 
binaries then there needs to be a prefix on the bin dir too.

> Nothing in ~/.cabal looks prefixed to me, by default.  Maybe my cabal is
> just old.

The defaults are:

install-dirs user
   -- prefix: /home/simonmar/.cabal
   -- bindir: $prefix/bin
   -- libdir: $prefix/lib
   -- libsubdir: $pkgid/$compiler
   -- libexecdir: $prefix/libexec
   -- datadir: $prefix/share
   -- datasubdir: $pkgid
   -- docdir: $datadir/doc/$pkgid
   -- htmldir: $docdir/html
   -- haddockdir: $htmldir

that is, libs go in .cabal/lib/$pkgid/$compiler by default.

I just discovered that cabal isn't using the target $arch/$os though, so 
I've filed a bug: https://github.com/haskell/cabal/issues/1184

> Do I need to tell it where to find ghc-pkg, or does that not matter?

No, cabal will find it.

Cheers,
	Simon




More information about the ghc-devs mailing list