Aha! I think this turned out to be the trouble. THANK YOU!
Having said that, I didn't specify -framework Python explicitly, but distutils put that *and* the correct '-I' (but not '-L') line for the corresponding include directory within the correct version of the framework. I guess it was getting the wrong library? Anyway.. I appreciate your suggestion to use the oldest supported system, but it's getting harder to keep such system around! thanks again, -steve On Feb 18, 2013, at 2:38 PM, Ned Deily <n...@acm.org> wrote: > Another thing - and this may be significant. When using -framework > Python, I expect that build tool chain will follow the Versions/Current > link in the framework to find the appropriate version. As it stands, > Python 3 installs normally do not change that Current link. So it may > be possible that Python 2 include files and libraries are being used > wherever you have -framework Python. So you should ensure that, during > the build, the Library/Frameworks/Python.frameworks linked to from the > SDK has Current pointing to 3.2. Or change the build to avoid > -framework Python and link to the desired Framework -I and -L > directories directly. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
