From cf783eb1dbc09182ab9d1902bbab3b675caa1dc0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20v=2E=20L=C3=B6wis?= Date: Mon, 18 Sep 2006 06:23:06 +0000 Subject: [PATCH] Mention that GCC 4.1 is also affected, and that adding -fwrapv helps. --- README | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README b/README index 70e4d231d8f..b91e229115c 100644 --- a/README +++ b/README @@ -276,13 +276,16 @@ on these platforms without the special directions mentioned here, submit a documentation bug report to SourceForge (see Bug Reports above) so we can remove them!) +GCC 4.1, GCC 4.2: There is a known incompatibility between Python and GCC, - where GCC 4.2 takes an interpretation of C different from + where GCC 4.1 takes an interpretation of C different from prior GCC releases, in an area where C has undefined behaviour (namely, integer arithmetic involving -sys.maxint-1). - As a consequence, compiling Python with GCC 4.2 is not + As a consequence, compiling Python with GCC 4.1/4.2 is not recommend. It is likely that this problem will be resolved - in future Python releases. + in future Python releases. As a work-around, it seems that + adding -fwrapv to the compiler option restores the earlier + GCC behaviour. Unix platforms: If your vendor still ships (and you still use) Berkeley DB 1.85 you will need to edit Modules/Setup to build the bsddb185