RE: Difficulties compiling hmake / HaXml
I want to use HaXml, and since hmake is required first, I'm currently trying to build hmake with GHC. Unfortunately "make" fails; I get the above errors message.
What am I doing wrong here?
I use GHC4.08.2 (InstallShield version) under WinNT4/Cygwin1.1.8.
If you have GHC 4.08.2, then you already have HaXML :-) It's in -package text. You should also have the HaXML utilities: DrIFT, DtdToHaskell, XTract.
make[1]: Entering directory `/test-hmake/hmake-2.02/src/interpreter' mkdir -p /test-hmake/hmake-2.02/targets/ix86-CYGWIN_NT-4.0/obj/interpreter /test-hmake/hmake-2.02/script/hmake -ghc HInteractive -d/test-hmake/hmake-2.02/t argets/ix86-CYGWIN_NT-4.0/obj/interpreter
Fail: Can't find module Posix in . Or in standard libraries at /ghc/ghc-4.08.2/lib/imports/std /ghc/ghc-4.08.2/lib/imports/data /ghc/ghc-4.08.2/lib/imports/lang /ghc/ghc-4.08.2/lib/imports/posix /ghc/ghc-4.08.2/lib/imports/net /ghc/ghc-4.08.2/lib/imports/num /ghc/ghc-4.08.2/lib/imports/text /ghc/ghc-4.08.2/lib/imports/util /ghc/ghc-4.08.2/lib/imports/win32 /ghc/ghc-4.08.2/lib/imports/concurrent Asked for by: HmakeConfig.hs [Check settings of -I or -P flags?]
Hmake needs Posix, which isn't supported on Windows, sorry. Cheers, Simon
If you have GHC 4.08.2, then you already have HaXML :-) It's in -package text. You should also have the HaXML utilities: DrIFT, DtdToHaskell, XTract.
Unfortunately, although HaXML should indeed be in the InstallShield, the associated tools are not in the binary distribution. This is an oversight which I'll rectify ASAP. -- http://sc3d.org/rrt/ | humour, n. unexpected recognition
Hmake needs Posix, which isn't supported on Windows, sorry.
The first part of this statement isn't strictly-speaking true. The batch part of hmake does not require Posix. The interactive interface (hi) may require Posix, but only if you build it with GHC and only if the readline library is available. If you don't want to use hi, or if you don't care about using readline's editing facilities inside hi, then you could simply disregard the errors. [ Really I should provide a configure option to disable readline. Until then, you can hack the file lib/$(MACHINE)/config. Just change the line READLINE="-DUSE_READLINE=1 -lreadline" to READLINE="" and the build should go smoothly again. (Provided you don't issue another ./configure command) ] Regards, Malcolm
participants (3)
-
Malcolm Wallace -
Reuben Thomas -
Simon Marlow