Update to compile under recent Haskell Platform
Closed this issue · 3 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Install Haskell-platform >=11.0
2. cabal install
What is the expected output? What do you see instead?
Expected: completed build of Haskell LSLForge
Actual: irreconcilable package dependencies, varying depending on specific
installation
What version of the product are you using? On what operating system?
current git head (0.1.2)
Please provide any additional information below.
As far as I can tell, it is difficult (impossible?) to compile on recent OSX,
as the suggested ghc is 6.10.4. But versions prior to 6.12 had issues on OSX
with generating 32bit executables. More recent versions do not support the
older versions of dependencies required by LSLForge, for instance:
haskell98-1.1.0.1 requires array ==0.3.* but LSLForge requires array ==0.2.*
Original issue reported on code.google.com by mth...@gmail.com on 22 Aug 2012 at 12:04
GoogleCodeExporter commented
It would be a helpful stopgap to publish a list of specific versions known to
work. I'm trying out the current latest haskell-platform and using "cabal-dev
install-deps"
Original comment by mth...@gmail.com on 27 Sep 2012 at 3:13
GoogleCodeExporter commented
Our plan is to phase out the haskell component and reimplement as a pure java
library. In the meantime, a few observations:
- The haskell component does compile with the 2009 libraries. In order to
build lslforge, the dependencies have to be built in a specific order. The
technique I've found that had minor success was to run "cabal install
--dry-run", install the topmost missing dependency, repeat.
- The OS X build system can compile 32-bit, but there is a known issue in GHC
10.4 that causes it to crash on 64-bit Macs. There is a manual fix to force
GHC to build a 32-bit binary.
If there is an interest in doing this, I can compile docs on how to reproduce
the build cycle on mac/linux/windows.
Original comment by elnew...@gmail.com on 26 Oct 2012 at 3:08
- Changed state: WontFix
GoogleCodeExporter commented
I am very interested in this - Given the plans to phase it out, I wouldn't want
you to spend all that much time on docs, but even a log or order on one OS
architecture would be useful.
Original comment by mth...@gmail.com on 26 Oct 2012 at 3:57