Re: Driver, build process, IOError



About this list Date view Thread view Subject view Author view

Malcolm Wallace (malcolm-nhc@cs.york.ac.uk)
Fri, 12 Jan 2001 21:35:10 +0000


> nhc98 exits with status 0 even if there was a compilation error. > It confuses e.g. make. This applies only to CVS versions from the last week or so. Now fixed. > The current CVS version of nhc tries to compile Int.hs.cpp and > Word.hs.cpp with g++ (!). Also applies to CVS only. Also now fixed. > `sudo make install' can turn /dev/null into a normal file, depending > on the compiler used to compile nhc (nhc's build process calls $(HC) > with -o /dev/null). This was a nasty one. For the 1.00 release, I think it only happens if you build the compiler as root, rather than just installing it. I would suggest that that is a dangerous thing to do anyway. However, for CVS versions since October, it also happens when simply installing. The latter is now fixed in CVS, and I shall fix the root-when-building problem shortly. > FFI in ghc and QForeign (and perhaps future standard FFI) assumes > that it is possible to implement the following function: > > errnoToIOError :: String -- location (function name) > -> Errno -- errno > -> Maybe Handle -- handle > -> Maybe String -- filename > -> IOError > newtype Errno = Errno CInt > > so it would be great if nhc exported something in terms of which such > errnoToIOError could be defined. Will do. It will probably be called IO.mkIOError. Regards, Malcolm


About this list Date view Thread view Subject view Author view