Hi,
I have received the following error message when
compiling the "Hello World" program:
$ ghc -o main main.hs
Compilation IS NOT required
gcc: C:/ghc/ghc-4.08.1/lib/Main.dll_o: No such file or directory
gcc: C:/ghc/ghc-4.08.1/lib/PrelMain.dll_o: No such file or directory
.
Als
* Simon Marlow <[EMAIL PROTECTED]> [2001-01-15T04:52-0800]:
> Volker previously wrote:
> [SIGTTOU when background process writes to terminal]
> This is truly bizarre. I've tracked it down to a tcgetattr/tcsetattr
> pair in setBuffering.
[...]
> What's weird is that the tcsetattr doesn't affect
* Michael Weber <[EMAIL PROTECTED]> [2001-01-16T00:00+0100]:
[...]
> So, a solution seems to be, to block SIGTTOU during the call of
> tcsetattr
[...]
BTW: Eventually, the following functions need the same shielding:
tcsetattr, tcsendbreak, tcflow, tcflush
Cheers,
M/
--
() ASCII ribbo
> So it seems that there is possibly a feature/bug in the C library
> such that calling tcsetattr() always suspends a backgrounded process,
> regardless of the setting of TOSTOP. As yet, I haven't been able to
> find a workaround. :-(
Yes, I went through a similar set of diagnoses myself after
> But we're not changing any of the terminal flags, simply setting
> the same ones again.
> I'm totally stumped! Any ideas, anyone?
According to the manual page,
tcgetattr() ... This function may be invoked
from a background process; however, the termina
> In fact I can produce a simple example, either. So just the facts:
>
> perftest@monster [11:46:35]> ./Reader &
> [2] 86029
> perftest@monster [11:46:40]> jobs
> [2]+ Stopped ./Reader
>
> Sourcecode-snippet of Reader:
>
> > main = do
> > -- Posix.installHandler Posix.sigTTOU
Incredibly tiny nit, but in the final section about compiling stubs,
I believe you mean -fPIC as the gcc option (the documentation says
-fPCI, which isn't something gcc recognizes).
You might also want to point out that debian packages are available
for apt-get'ting, at least you run woody.
Oth
This is an error from the C compiler (not GHC), while it was trying to
write the assembly file. It probably indicates a problem with your
system - a faulty disk or problems with an NFS mount, perhaps?
Cheers,
Simon
-Original Message-
From: Shi Kun [mailto:[EMAIL PROTECTED]]
Sent: S
Hello,
I got the following error msg when I compiled my
.hs program with GHC-4.04 on
unix platform (SunOS 5.7)
cc1:
ghc16082.s: I/O error
May I know whether it is my program's error, GHC
error or sun system's error?
Regards,
shikun
