diff options
| author | Martin v. Löwis <martin@v.loewis.de> | 2006-09-18 06:23:06 (GMT) |
|---|---|---|
| committer | Martin v. Löwis <martin@v.loewis.de> | 2006-09-18 06:23:06 (GMT) |
| commit | cf783eb1dbc09182ab9d1902bbab3b675caa1dc0 (patch) | |
| tree | 447213d3acb5374640f9d99dc4081122fad74d82 /README | |
| parent | 885d8e773765206670c91f3eb92b6c117ba70de8 (diff) | |
| download | cpython-cf783eb1dbc09182ab9d1902bbab3b675caa1dc0.zip cpython-cf783eb1dbc09182ab9d1902bbab3b675caa1dc0.tar.gz cpython-cf783eb1dbc09182ab9d1902bbab3b675caa1dc0.tar.bz2 | |
Mention that GCC 4.1 is also affected, and that
adding -fwrapv helps.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 9 |
1 files changed, 6 insertions, 3 deletions
@@ -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 |