This was a grevious bug in 6.0, fixed in 6.0.1. I believe
Simon
| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:glasgow-haskell-bugs-
| [EMAIL PROTECTED] On Behalf Of Till Mossakowski
| Sent: 15 October 2003 17:21
| To: [EMAIL PROTECTED]
| Subject: GHC 6.0 (Sparc-Solaris) bug
|
On Windows, Hugs' implementation of System.system always returns ExitSuccess
because the Windows routine it calls doesn't return a useful exit status.
Thanks, I hadn't noticed before, but you're right: Hugs suffers from the same bug.
My very vague memory from looking into this some years
Please, what is the matter with the packages in ghc-6.0.1 ?
(ghc-6.0.1
installed from RPM on Red Hat Linux release 7.3 (Valhalla),
i-386 unknown
)
It does not find the library items, say List.sort,
when it `makes' under the user package in the user project
importing standard
Dear GHC team,
ghc-6.0.1
installed from RPM on Red Hat Linux release 7.3 (Valhalla)
i-386 unknown
runs into the following bug after `making' of my large project and
when running the test
T_.test log
from Interpreter:
...
finds gs' = Groebner basis gs,
tests
addition to the previous bug report on
interactive: internal error: scavenge
:
when the project is made under -O, this bug is not revealed
(but it may, for example, appear under different memory options,
who knows).
___
Glasgow-haskell-bugs
I suspect that may previous bug report on interactive interpreter
should be replaced with the following one, which is simple to
analyse.
This is on
ghc-6.0.1
installed from RPM on Red Hat Linux release 7.3 (Valhalla),
i-386 unknown.
Probably, you can reduce the example several times
Serge D. Mechveliani wrote:
[...] /home/mechvel/test/export/HSdocon.o: unknown symbol `__stginit_List_'
[...] Then, occasionally, tried to set package_deps = [data]
, even though my contrived user package does not use data.
And it started to work, to load everything needed!
Then I try
[Sorry if this shows up twice -- I accidentally posted from the wrong address
and left something out.]
I have a program, compiled with cost-center profiling on, that takes about 5
minutes, 30 seconds to run (measured with a stopwatch), but the resulting .prof
file reports the total time as 34
