On Nov 30, 2010, at 8:41 AM, Christopher Barker wrote: > On 11/30/10 12:30 AM, Larry Bugbee wrote: >> Something's still wrong but I cannot spend much more time on this. I'd do >> well to stick with 2.6.5 and try again in a couple of weeks. > > Does (one of) the python.org 2.7 (2.7.0) build not support readline? It's > hidden on the site, but can be found here: > > http://www.python.org/download/releases/2.7/ > > I haven't gone to 2.7 yet -- I suppose it's time...
I went there, downloaded the 32- and 64-bit pre-built versions of 2.7.1, and both worked. For now I'm good to go. ...but why my build failed still escapes me. Amongst many trials I used MACOSX_DEPLOYMENT_TARGET=10.6 ./configure --enable-framework make sudo make install and ./configure --enable-framework MACOSX_DEPLOYMENT_TARGET=10.6 make sudo make install I also exported MACOSX_DEPLOYMENT_TARGET=10.6 to be sure all that needed it could see it. ...but No Joy. I kept getting responses to the up arrow like this... >>> 111 111 >>> ^[[A^[[A ...which I take as a readline-related problem. readline (gnu) and editline (libedit) were installed, and reinstalled. Paths were checked. Both /Developer/SDKs/MacOSX10.5.sdk and /Developer/SDKs/MacOSX10.6.sdk are installed. (the 10.3 and 10.4u SDKs are not installed) gcc -v returns "gcc version 4.2.1 (Apple Inc. build 5664)" and I'm running OSX 10.6.5. Dunno. Perhaps I was trying to build an "illegal" combination of 1) 10.6 (or 10.5, tried both) via the MACOSX_DEPLOYMENT_TARGET specification and 2) the older 32-bit 10.3 by naively not saying the right words to ./configure. Or perhaps I was attempting a 32- and a 64-bit link and missed the error message. I don't think so, but at this point, who knows? I'll keep looking and trying, but for now I'll have to move this to a back burner. Thanks all for the tips and suggestions. Larry
