Patches item #1779871, was opened at 2007-08-23 00:02 Message generated for change (Comment added) made by marketdickinson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1779871&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Python 2.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jeffrey Yasskin (jyasskin) Assigned to: Nobody/Anonymous (nobody) Summary: Make python build with gcc-4.2 on OS X 10.4.9 Initial Comment: I tested the change with Apple's gcc and gcc-4.2, but only on an Intel mac. http://gcc.gnu.org/ml/gcc/2005-12/msg00368.html says that -no-cpp-precomp is obsolete, and there weren't any warnings about long doubles, so I just removed those two, and because I'm paranoid, I added a test compile for -mno-fused-madd. ---------------------------------------------------------------------- Comment By: Mark Dickinson (marketdickinson) Date: 2007-08-23 04:15 Message: Logged In: YES user_id=703403 Originator: NO Also works for me on a PowerPC mac (OS X 10.4.10/G4), with gcc4.2 from macports: compiles successfully and all tests pass. This should fix bug 1450807. What happens with earlier versions of OS X? It looks as though the -Wno-long-double flag was added just to suppress warnings, so nothing dire should happen if it's removed. Might the -no-cpp-precomp still be required for 10.2 or earlier? Would it make sense to remove these two flags only for 10.3 and above, or only when using non Apple-supplied gcc? Or to test for existence of the -no-cpp-precomp flag? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1779871&group_id=5470 _______________________________________________ Patches mailing list Patches@python.org http://mail.python.org/mailman/listinfo/patches
