Looks like invalid installation. My IMHO is as follows:

0) Read carefully "Setting up GHC on Win32 platforms" by Sigbjorn Finne on GHC WWW 
page. Your primary goal is to get cygwin32 be correctly installed.

1) Be shure you have cygwin version 20.1 installed. If not, uninstall installed 
cygwin, get cygwin 20.1 (The main WWW page for the Cygwin project is 
http://sourceware.cygnus.com/cygwin/. A page containing tool-specific information is 
http://www.cygnus.com/pubs/gnupro/. Links to additional documentation are accessible 
from the main web page. ). Also you should get EGCS-1.1.2 for cygwin binaries to 
replace GCC and brothers.

2) Read Cygwin FAQ and User Manual (see Cygwin homepage).

3) You should start bash via batch file cygnus.bat only 
(h:\cygnus\cygwin-b20\cygnus.bat).
This file should contain environment variable PATH (e.g, SET 
PATH=h:\cygnus\cygwin~1\H-i586~1\bin;%PATH%) that sets cygnus bin directory in the 
first place, among other variables (see FAQ and installation instructions).

4) You should have (create) directories /usr, /bin, /var (/var/log), /etc. The bin 
directory should contain sh.exe (that is, in general, copy of bash.exe). Or, you can 
create symbolic link for /bin to be as /cygnus/cygwin-b20/H-i586-cygwin32/bin (I have, 
e.g., such link).

5) Check your mounts: say "mount" at bash prompt and check output. You should have (in 
your case) root directory be mounted as H:\\.

6) Remeber that Windows 95/98 is not the best choice to run cygwin (mostly, due to 
poor Win32 API). Windows NT 4.0 (SP3 or SP4, SP standing for Service Pack) would be 
better.

7) If you can't solve the problem, you should run "cygcheck -s -v -r" at bash prompt 
and send the output with the description of your problem to "someone who can help" (if 
I can I will try).

8) If "someone" can't help you, you can subscribe to cygwin mail list (see FAQ) to ask 
about it.

Good luck and Best Wishes,

Michael

P.S. By the way, I had Windows95 (afterwards Windows98) installed previously and there 
were problems with cygwin. Now I have NT 4.0 SP4 installed and no Windows9x-like 
problems.

-----Original Message-----
From: Dion McMurtrie <[EMAIL PROTECTED]>
To: Michael V. Nikolaev <[EMAIL PROTECTED]>
Cc: GHC bugs mail-list <[EMAIL PROTECTED]>
Date: 29 aadaciy 1999 d. 18:49
Subject: Re: problem setting up GHC on Win32


>I tried this.  The directory is there and accessable in win95, but when I
>run the cygwin bash shell I still get the error message that the /tmp
>directory should be created.  If I change directories to the root directory
>and then try to chang into the tmp directory this happens -
>
>DETLOG.OLD                            ahis.htm
>DETLOG.TXT                            assignment1p95.rtf
>Diablo                                bin
>Eudora                                cal98_ge.pdf
>Exchange                              ffastun.ffa
>FILE0000.CHK                          ffastun.ffl
>Fitsh.c                               ffastun.ffo
>IO.SYS                                ffastun0.ffx
>IO32.IDX                              ghc1015.hs
>JGLBatchFileSetup.001                 ghc1023.hs
>MAKEFILE                              os1981.txt
>MOUSE                                 pk250w32.exe
>MSDOS.---                             single_0.sv
>MSDOS.SYS                             single_1.sv
>My Documents                          tmp
>NETLOG.TXT                            v95i314e.zip
>New Microsoft Publisher Document.pub
>BASH.EXE-2.02$ pwd
>/
>BASH.EXE-2.02$ cd tmp
>BASH.EXE-2.02$ pwd
>/
>BASH.EXE-2.02$ ls -l tmp
>ls: tmp: No such file or directory
>BASH.EXE-2.02$
>
>The top part is a directory listing (ls) of the root directory and as you
>can see second from the bottom on the right hand side is the directory tmp.
> But when I try to change directory to it, nothing seems to happen.  When I
>try to do an "ls -l tmp" it says the directory doesn't exist.
>
>I have tried deleting the directory with win95 and re-createing it with
>both win95 and cygwin, and neither works.  What am I doing wrong?
>
>At 18:53 27/03/1999 +0200, Michael V. Nikolaev wrote:
>>Try to create /tmp from Windows environment, not from cygwin bash shell.
>>
>>Regards,
>>Michael
>>
>>-----Original Message-----
>>From: Dion McMurtrie <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>>Date: 27 aadaciy 1999 d. 17:13
>>Subject: problem setting up GHC on Win32
>>
>>
>>>I'm having trouble setting up GHC on Win32.
>>>
>>>I can install the cygwin B20 software and run it.  As soon as I run it it
>>>complains that -
>>>
>>>bash.exe: warning: could not find /tmp, please create!
>>>BASH.EXE-2.02$
>>>
>>>If I try to make the /tmp directory by typing "mkdir -p /tmp" or "mkdir
>>>/tmp" I get the error -
>>>
>>>BASH.EXE-2.02$ mkdir /tmp
>>>mkdir: cannot make directory `/tmp': No such file or directory
>>>BASH.EXE-2.02$ mkdir -p /tmp
>>>mkdir: cannot create directory `/tmp': No such file or directory
>>>BASH.EXE-2.02$
>>>
>>>What am I doing wrong?
>>>
>>>The cygwin software is installed to h:\cygwin
>>>ghc is installed to h:\ghc
>>>I'm running Windows 95
>>>
>>>Nothing else wants to run without the /tmp directory set up (perl and the
>>>configure scripts both complain about the /tmp directory).
>>>
>>>I'm running ghc under Linux with no hassles, but I need to compile a
>>>Haskell program for Win32, and thought that setting up ghc for Win32 would
>>>be the best way to do this.
>>>
>>>Actually it would be really good to be able to compile my Haskell code to
>>>some intermediate language that I could compile anywhere.  For example
>>>compile to C under Linux, and then use the gcc compiler on any UNIX box to
>>>make a useable binary - is there a way to do this?  I can't get the .hc
>>>code output of the ghc compiler to compile with gcc, is there a way to do
>>>something like this?
>>>
>>>Thanks in advance,
>>>
>>> - Dion McMurtrie.
>>>
>>
>============================================================================
>====
>"For I perceive that behind this seemingly unrelated sequence of events,
>there lurks a singular, sinister attitude of mind."
>
>"Whose?"
>
>"MINE! HA-HA!"
>


Reply via email to