RE: HDirect and GHC 4.03 installation and example compile problem s

[Sigbjorn Finne (Intl Vendor)]

Mike Thomas <[EMAIL PROTECTED]> writes:
> 
> Hi whomever.
> 
...
> --------------------------------------------------------------
> --------------
> 1.   When I use the Win32 binary installer for HDirect, it 
> fails to find the GHC home directory unless GHC (the 4.03
> binary distribution) was installed in the default location.
> This means that the libraries and interfaces have
> to be installed by hand.
> 

Hi,

odd - I haven't experienced this here nor can I reproduce it now
(on an NT box). The InstallScript code looks in 

  HKLM\Software\Haskell\Glasgow Haskell Compiler\ghc-4.03\{bin,lib}dir

for info on where to install the HDirect library and interface files.
Do these point to the GHC install in your case?

> --------------------------------------------------------------
> --------------
> 2.  Compiling the comcli example fails because there is no 
> stdole interface
> (GHC 4.03 binary distribution):
> 
> BASH.EXE-2.02$ make
> ghc -fglasgow-exts -syslib com -fno-warn-missing-methods    
> -c Ielabel.hs -o
> Ielabel.o -osuf o
> 
> Ielabel.hs:15: Could not find valid interface file `Stdole32'
> 
> Compilation had errors
> 

Add -fignore-source-interfaces to SRC_IHC_OPTS in Makefile
to make this one go away.

> make: *** [Ielabel.o] Error 1
> 
> --------------------------------------------------------------
> --------------
> 3.  Compiling the examples using the makefiles provided 
> requires changes of references to libhdirect to libHScom.
> 

Yep, thanks - fixed this in the current sources.

> --------------------------------------------------------------
> --------------
> 4.  A couple of examples that I have compiled crash on execution.
> 
>     GD - haven't tracked the crash point down
> 
> 
>     listdir - Executed without command line options, crashes 
> after printing
> "Usage:"  - the v seems to cause the problem.  If removed 
> from the string concatenation the program doesn't crash.
> 

I suspect this all down to the bug which the ghc-4.03 patch 
fixes (available via the ghc-win32 pages), i.e., trouble with
using System.{getProgName, getArgs}.

Thanks for the report,

--sigbjorn