[issue2626] If compile with gcc 4.3.0 python interpreter itself eats all memory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: That's a bug in gcc 4.3, see http://mail.python.org/pipermail/python-3000/2008-April/012965.html -- nosy: +loewis resolution: -> invalid status: open -> closed versions: +3rd party -Python 3.0 __ Tr

[issue2626] If compile with gcc 4.3.0 python interpreter itself eats all memory

Georgij Kondratjev <[EMAIL PROTECTED]> added the comment: This doesn't affect python 2.5.2 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing

[issue2626] If compile with gcc 4.3.0 python interpreter itself eats all memory

New submission from Georgij Kondratjev <[EMAIL PROTECTED]>: First time I noticed it during compilation of python3 r62301, then 3.0a4, then 3.0a3, with and without CFLAGS set. Step "./python -E ./setup.py -q build" called by make never ends (and there is no output). Just "/python" behaves the s