Closed CarstenKoenig closed 9 years ago
How are you specifying the package sandbox location? Also note that the fay executable and fay-base needs to be installed in the same sandbox. You should also make sure that you don't have two versions of fay-base installed since I recall seeing errors like this for that case as well.
It may very well be a windows issue though, I have never used fay on windows myself.
I tried this under windows, linux and osx (every time with the same sandbox-setup) and only on windows I get this issue.
I choose the location with the parameter argument to fay (I couldn't get the env.variable thing going at all) and basically I just did
cabal update
cabal sandbox init --sandbox=.
cabal install fay
cabal install fay-base
so it should all be there (and is on linux/osx)
So yeah I think it's some strange windows / pathing thing
One way to debug this is to add some tracing for flags
in Fay.Compiler.Typecheck
to see what is passed to ghc.
ok - I have not much time right now but I'll to get something done tomorrow - thanks for your help
Spring cleaning. Lack of activity.
I tried installing fay and fay-base into a local sandbox under windows. When I try to compile a simple file using fay I always get this (when giving the absolute path to the
x...-packages.conf.d
):When I look into the packages both libs with the correct version are there.
The same situation under Linux: everything works, so I guess it's some strange windows/path issue?