
AFAIK GHC on Windows comes with it's own mingw, but I'm not sure if the
toolchain is complete. But I wouldn't try to reinstall core packages anyway.
They are best picked from installation package.
Best regards,
Krzysztof Skrzętnicki
2011/2/1 Arnaud Bailly
I started that way but quickly ran into issues about compilers toolchain for certain packages: I am on windows and some core packages require mingw toolchain.
2011/2/1 Krzysztof Skrzętnicki
: This is the easiest way conceptually. You can also try to --reinstall every package that 'ghc-pkg check' report is broken. If you pick up the right version and compilation options will match there is a high chance you can fix this state. I've done this before and it worked. Best regards, Krzysztof Skrzętnicki
On Tue, Feb 1, 2011 at 08:16, Arnaud Bailly
wrote: Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote:
On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly < arnaud.oqube@gmail.com> wrote:
Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe