Cabal uses something like system "ghc --version >tmp" in order to
determine the version of GHC. After the last changes in CVS the above
line no longer produces the right result. The temporary file is
created but it is empty. It seems like the stdout/stderr handles are
flushed in GHC.TopHandler.runM
All,
Okay, I've done due diligence on this problem and haven't found any solution,
so I figured that I'd spam the list for help.
System: Gentoo Linux (freshly emerged...)
Pentium 3
GCC 3.3.4
I'm trying to build cvs-HEAD and am having problems. The build completes just
f
Alson Kemp wrote:
[...] I'm trying to build cvs-HEAD and am having problems. The build
completes just
fine, but the built GHC 6.3 does not include the "-I" include directories
option for GCC. [...]
I've just stumbled over exactly the same problem in this second, and I'm
already investigating wha
This should be fixed now. The fastest way to a working installation is to
simply update the toplevel "mk" directory, remove all "package.conf.installed"
files, and do a "make install".
Cheers,
S.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-u
The temporary file is
created but it is empty. It seems like the stdout/stderr handles are
flushed in GHC.TopHandler.runMainIO but only if the program terminates
without exception.
Should be fixed now; when terminating using exitWith, the handles are
now flushed.
Note that they are still not flush
> This should be fixed now.
Just updated and built. Everything works perfectly now.
Thank you.
- Alson
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
On Sun, Jan 23, 2005 at 03:22:55PM -0500, Wolfgang Thaller wrote:
> >The temporary file is
> >created but it is empty. It seems like the stdout/stderr handles are
> >flushed in GHC.TopHandler.runMainIO but only if the program terminates
> >without exception.
>
> Should be fixed now; when terminati
It seems they should always be flushed. certainly if a program fails
via
'fail' in IO or 'error' as these are common ways for programs to report
an error and losing output would definitly be counter intuitive and
make
it quite tricky to debug. especially when you can't flush stdout before
calling