That didn't work, BUT then I realized that I somehow downloaded the tarball for 0.90, and not the current 0.91.3. Not sure where I got it from. In any case, the Mac instructions specifically say 0.90.1 or higher. My apologies for missing that. Now I'm having a problem compiling only a 64-bit version of PyOpenCL. My python and boost installations in MacPorts are only 64-bit so I modified my config command to look like: python configure.py \ --boost-inc-dir=/opt/local/include \ --boost-lib-dir=/opt/local/lib \ --boost-python-libname=boost_python-mt \ --boost-thread-libname=boost_thread-mt \ --cl-libname='' \ --ldflags='-Wl,-framework,OpenCL,-arch x86_64' \ --boost-compiler='gcc42' \ --python-exe=/opt/local/bin/python \ --cxxflags='-arch x86_64' \ However, during make, it's not recognizing the already-existing -arch in cxxflags, resulting in commands like /usr/bin/gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -fwrapv -Wall -O3 -DNDEBUG -I/opt/local/include -Isrc/cpp -I/opt/local/include -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/numpy/core/include -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c src/wrapper/wrap_cl.cpp -o build/temp.macosx-10.6-i386-2.6/src/wrapper/wrap_cl.o -arch x86_64 -arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk with "-arch x86_64 -arch i386 -arch x86_64" in them. So I went manually into setup.py and changed lines 60-70 to: if 'darwin' in sys.platform: # Build for i386 & x86_64 since OpenCL doesn't run on PPC if "-arch" not in conf["CXXFLAGS"]: #conf["CXXFLAGS"].extend(['-arch', 'i386']) conf["CXXFLAGS"].extend(['-arch', 'x86_64']) if "-arch" not in conf["LDFLAGS"]: #conf["LDFLAGS"].extend(['-arch', 'i386']) conf["LDFLAGS"].extend(['-arch', 'x86_64']) # Compile against 10.6 SDK, first to support OpenCL conf["CXXFLAGS"].extend(['-isysroot', '/Developer/SDKs/MacOSX10.6.sdk']) conf["LDFLAGS"].extend(['-isysroot', '/Developer/SDKs/MacOSX10.6.sdk']) commenting out lines 63 and 66, which specify i386 architecture. Changed my config command to: python configure.py \ --boost-inc-dir=/opt/local/include \ --boost-lib-dir=/opt/local/lib \ --boost-python-libname=boost_python-mt \ --boost-thread-libname=boost_thread-mt \ --cl-libname='' \ --ldflags='-Wl,-framework,OpenCL' \ --boost-compiler='gcc42' \ --python-exe=/opt/local/bin/python \ And it installed. However, in python: Fatal Python error: Interpreter not initialized (version mismatch?) Abort trap Any ideas? Faisal

Andreas, Thanks for all your help so far. Here is the output of otool -L for _cl.so, located at: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyopencl-0.91.3-py2.6-macosx-10.6-i386.egg/pyopencl/_cl.so $ otool -L _cl.so _cl.so: /opt/local/lib/libboost_python-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_thread-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0) $ file _cl.so _cl.so: Mach-O 64-bit bundle x86_64 However: $ otool -L /opt/local/lib/libboost_python-mt.dylib /opt/local/lib/libboost_python-mt.dylib: /opt/local/lib/libboost_python-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /System/Library/Frameworks/Python.framework/Versions/2.6/Python (compatibility version 2.6.0, current version 2.6.1) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) Note that it links to the system python. This is a MacPorts bug (http://trac.macports.org/ticket/21444). I relinked the libboost_python-mt library by hand to the MacPorts python installation using instructions at the MacPorts trac page. After that, I had no problems running "import pyopencl". However, "make tests" fails soon after the import. $ make tests echo "running tests" running tests find ./test -type f -name "*.py" -exec python {} \; Traceback (most recent call last): File "./test/test_wrapper.py", line 303, in <module> from py.test.cmdline import main ImportError: No module named cmdline Not a huge problem for me. I just went into the examples dir and ran benchmark-all.py. Seems to work. Thanks for the help again, Andreas. Faisal