This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | jyasskin |
|---|---|
| Recipients | jyasskin, mark.dickinson, ronaldoussoren |
| Date | 2008年01月17日.07:09:36 |
| SpamBayes Score | 0.0017448338 |
| Marked as misclassified | No |
| Message-id | <1200553792.14.0.828970257022.issue1779871@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Sorry for taking so long to get to this. gcc 4.2.1 still produces the following errors with this patch: gcc -c -fno-strict-aliasing -mno-fused-madd -no-cpp-precomp -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I/opt/local/include -DPy_BUILD_CORE -o Objects/boolobject.o Objects/boolobject.c gcc: unrecognized option '-no-cpp-precomp' cc1: error: unrecognized command line option "-mno-fused-madd" make: *** [Objects/boolobject.o] Error 1 I see you dropped the test for -mno-fused-madd. Since gcc-4.2 doesn't support it, I meant I didn't mind if you dropped the flag entirely. It looks like -no-cpp-precomp stuck around because it doesn't actually cause the compile to fail, just to produce a warning message. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月17日 07:09:52 | jyasskin | set | spambayes_score: 0.00174483 -> 0.0017448338 recipients: + jyasskin, ronaldoussoren, mark.dickinson |
| 2008年01月17日 07:09:52 | jyasskin | set | spambayes_score: 0.00174483 -> 0.00174483 messageid: <1200553792.14.0.828970257022.issue1779871@psf.upfronthosting.co.za> |
| 2008年01月17日 07:09:36 | jyasskin | link | issue1779871 messages |
| 2008年01月17日 07:09:36 | jyasskin | create | |