
If you're on Windows install development environments outside the Programs
Folder which has special protections on it.
--
--
Sent from an expensive device which will be obsolete in a few months! :D
Casey
On Jan 30, 2015 2:33 PM, "Henk-Jan van Tuyl"
On Fri, 30 Jan 2015 14:54:36 +0100, Gregory Guthrie
wrote: Doing a cabal update, it notes a new version of cabal -install, so trying
that fails, and now it looks like cabal itself is broken (no installs work). Any short-term \remedies, and/or long term better approaches?
A method that usually works is as follows: md CabalInstall cd CabalInstall cabal sandbox init cabal install cabal-install Then copy CabalInstall\.cabal-sandbox\bin\cabal.exe to the location of the old cabal.exe (probably something like "C:\Program Files\Haskell Platform\2014.2.0.0\lib\extralibs\bin\" (Maybe rename the old cabal.exe to cabal-1.20.0.4.exe (or something similar) first) Check with cabal --version if the correct version of cabal.exe is run.
If you are using a sandbox, all locally installed packages are ignored, so there is less chance of dependency problems.
Regards, Henk-Jan van Tuyl
-- Folding@home What if you could share your unused computer power to help find a cure? In just 5 minutes you can join the world's biggest networked computer and get us closer sooner. Watch the video. http://folding.stanford.edu/
http://Van.Tuyl.eu/ http://members.chello.nl/hjgtuyl/tourdemonad.html Haskell programming -- _______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners