On Tue, Dec 8, 2009 at 10:40 AM, Rush Manbert <[email protected]> wrote:
> ...snipped for brevity... > running build_ext > building 'thrift.protocol.fastbinary' extension > creating build/temp.macosx-10.3-fat-2.5 > creating build/temp.macosx-10.3-fat-2.5/src > creating build/temp.macosx-10.3-fat-2.5/src/protocol > gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk > -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd > -fno-common -dynamic -DNDEBUG -g -O3 > -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c > src/protocol/fastbinary.c -o > build/temp.macosx-10.3-fat-2.5/src/protocol/fastbinary.o > cc1: error: unrecognized command line option "-Wno-long-double" > cc1: error: unrecognized command line option "-Wno-long-double" > lipo: can't figure out the architecture type of: > /var/folders/nm/nmKijaXB2Ra4W++BYmpzzU+++TI/-Tmp-//ccrUZKEd.out > error: command 'gcc' failed with exit status 1 > I think this must have been some peculiarity of your nonstandard install. I grepped for "no-long-double" and it's nowhere in the source. I bet the build_ext task you had installed was inserting this parameter which isn't supported by the version of gcc you're running post-upgrade. Given you had success with the standard install, is that a +1 from you? So far we have +1s from Todd (ie me), Jake, Bryan, and Joe. So that's 3 committers and one IPMC. As I understand it we need two more IPMC +1s after emailing the incubator-general list. I'll take care of posting there towards the end of the day today. Thanks -Todd
