On Dec 8, 2009, at 10:55 AM, Todd Lipcon wrote: > 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.
There have been a few oddities after the move to Snow Leopard, so I wouldn't be surprised. > > Given you had success with the standard install, is that a +1 from you? I'm afraid not. See my subsequent post. - Rush
smime.p7s
Description: S/MIME cryptographic signature
