Hi everyone: I was wondering, has anyone seen the following
compilation error for shim:

Shim/MessagesTH.hs:68:0:
    Warning: Definition but no type signature for `arity'
             Inferred type: arity :: forall t. (Num t) => Type -> t
[12 of 14] Compiling Shim.Messages    ( Shim/Messages.hs,
dist/build/shim/shim-tmp/Shim/Messages.o )
Loading package base ... linking ... done.
Loading package array-0.1.0.0 ... linking ... done.
Loading package containers-0.1.0.1 ... linking ... done.
Loading package parallel-1.0.0.0 ... linking ... done.
Loading package mtl-1.1.0.0 ... linking ... done.
Loading package old-locale-1.0.0.0 ... linking ... done.
Loading package old-time-1.0.0.0 ... linking ... done.
Loading package filepath-1.1.0.0 ... linking ... done.
Loading package directory-1.0.0.0 ... linking ... done.
Loading package unix-2.3.0.0 ... linking ... done.
Loading package process-1.0.0.0 ... linking ... done.
Loading package pretty-1.0.0.0 ... linking ... done.
Loading package Cabal-1.5.1 ... linking ... done.
Loading package parsec-2.1.0.0 ... linking ... done.
Loading package network-2.1.0.0 ... linking ... done.
Loading package hpc-0.5.0.0 ... linking ... done.
Loading package bytestring-0.9.0.1 ... linking ... done.
Loading package packedstring-0.1.0.0 ... linking ... done.
Loading package template-haskell ... linking ... done.
Loading package readline-1.0.1.0 ... linking ... done.
Loading package Cabal-1.2.3.0 ... linking ... done.
Loading package random-1.0.0.0 ... linking ... done.
Loading package haskell98 ... linking ... done.
ghc-6.8.2: /usr/lib64/ghc-6.8.2/HSghc.o: unknown symbol
`directoryzm1zi0zi0zi0_SystemziDirectory_lvl19_closure'
Loading package ghc-6.8.2 ... linking ... ghc-6.8.2: unable to load
package `ghc-6.8.2'

? I am using the http://code.haskell.org/shim repo. (I don't believe
the docs cover where to get Shim from.)

--
gwern

--~--~---------~--~----~------------~-------~--~----~
Yi development mailing list
yi-devel@googlegroups.com
http://groups.google.com/group/yi-devel
-~----------~----~----~----~------~----~------~--~---

Reply via email to