Dnia 06-04-2008, nie o godzinie 16:29 +0200, "Martin v. Löwis" pisze:
> Depending on how much you care about this issue, feel free to contribute
> a patch. The alternatives I see is
> a) do nothing (obviously), trusting that Google will find this thread
> b) add something to the README
> c) detect
> The bug is present in gcc-4.3.0 released a month ago, so someone with
> vanilla gcc-4.3.0 might check this. Adding -fno-tree-vrp is a workaround
> for gcc-4.3.0.
Depending on how much you care about this issue, feel free to contribute
a patch. The alternatives I see is
a) do nothing (obviously),
Dnia 06-04-2008, nie o godzinie 15:23 +0200, "Martin v. Löwis" pisze:
> What operating system and compiler? Does the behaviour change if you
> compile without optimization?
You are right, this is a gcc bug. Python built with OPT=-O0 passed to
configure. This is Linux/athlon, gcc-4.3.0 snapshot fr
> 3.0a4 doesn't build for me. A python process hangs spinning the CPU, and
> ^C yields:
What operating system and compiler? Does the behaviour change if you
compile without optimization?
Regards,
Martin
___
Python-3000 mailing list
Python-3000@python.or
3.0a4 doesn't build for me. A python process hangs spinning the CPU, and
^C yields:
Fatal Python error: Py_Initialize: can't initialize sys standard streams
Traceback (most recent call last):
File "/home/users/qrczak/Python-3.0a4/Lib/io.py", line 37, in
import warnings
File "/home/users/q
