> BTW: I've been doing gcc pre-release testing regularly for many year, > starting > with gcc 3.3. This is the first time I see the Python build fail persistently > for several weeks.
Wild guess: did configure detect that it needs to use -fno-strict-aliasing? Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
