Failure to build, MAC OSX 10.6.8 Xcode 4.2

Bug #967861 reported by Frank Buchanan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python-Crypto
New
Undecided
Unassigned

Bug Description

Am unable to build pycrypto-2.5 on one machine after successfully building, installing, and using it on a different machine earlier today. The SUCCESSFUL machine is running OSX 10.5.X on a PPC. I mention that machine only to indicate that I am able to follow the instructions in the README.

The UNSUCCESSFUL machine is running OSX 10.6.8 and xcode 4.2, Intel core duo, i386, Python 2.5.1. Upon doing "python setup.py build" everything seems to be going swimmingly until
  ...
 configure: creating ./config.status
 config.status: creating src/config.h
 warning: GMP or MPIR library not found; Not building Crypto.PublicKey._fastmath.
 building 'Crypto.Hash._MD2' extension
 creating build/temp.macosx-10.3-fat-2.5
 creating build/temp.macosx-10.3-fat-2.5/src
 Compiling with an SDK that doesn't seem to exist: /Developer/SDKs/MacOSX10.4u.sdk
 Please check your Xcode installation
 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 -std=c99 -O3 -fomit-frame-pointer -Isrc/ -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c src/MD2.c -o build/temp.macosx-10.3-fat-2.5/src/MD2.o
 llvm-gcc-4.2: error trying to exec '/usr/bin/../llvm-gcc-4.2/bin/powerpc-apple-darwin10-llvm-gcc-4.2': execvp: No such file or directory
 cc1: error: unrecognized command line option "-Wno-long-double"
 lipo: can't figure out the architecture type of: /var/folders/cy/cyIjb0tlFaKWFL7NTfwbLE+++TM/-Tmp-//ccspJXFb.out
 error: command 'gcc' failed with exit status 255

I note the "Please check your Xcode installation", which is why I indicated my Xcode version earlier. I am ahead of the curve xcode-wise for osx10.6, so perhaps this is the problem. (xcode 4.2 is not normally available for osx10.6 users). Or, perhaps that's just a red herring.

I also notice the build process fails while building a ppc version, which I don't want or need for this machine. Is there any way I can tell the build process to just build the version for this machine, and not to bother with a fat binary?

Thanks for any help,
Frank B

Revision history for this message
Darsey Litzenberger (dlitz) wrote :

This is a duplicate of LP#799985.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.