classification
Title: build failures on Snow Leopard
Type: compile error Stage:
Components: Build, Macintosh Versions: Python 2.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: ronaldoussoren Nosy List: ned.deily, richard, ronaldoussoren (3)
Priority: Keywords

Created on 2009-10-22 00:16 by richard, last changed 2009-10-22 06:18 by ned.deily.

Files
File name Uploaded Description Edit Remove
python-r75588-build.log richard, 2009-10-22 00:16 build log for r75588
Messages (2)
msg94331 - (view) Author: Richard Jones (richard) Date: 2009-10-22 00:16
I'm using python 2.6 maint SVN r75588 and get the attached build log
when I run:

  configure --enable-framework
  make

Failed to build these modules:
_curses            _curses_panel      _tkinter        
readline
msg94334 - (view) Author: Ned Deily (ned.deily) Date: 2009-10-22 06:18
Building a batteries-included framework on OS X is not a simple task, 
especially on 10.6 Snow Leopard where the system default is to build 64-
bit archs.  There are several known build issues with building a 
complete framework on 10.6.  It's not clear what your intentions are. If 
you want a 64-bit build with everything included, you'll need to supply 
a 64-bit version of readline (which is not included in OS X) and, prior 
to building, you may need to delete any already installed python.org (or 
other 3rd-party) version of python2.6 in 
/Library/Frameworks/Python.framework/Version/2.6: you may end up with 
dynamic linking to a 32-bit version of the ncurses libraries from there.  
And Tkinter and Tk are problematic: there are some unresolved problems 
using the 64-bit Apple-supplied Tk in 10.6.  If you don't need ncurses 
et al, just ignore the build errors.  If you do need them, your best bet 
is to use or adapt the OS X installer build script, 
Mac/BuildScript/build-installer.py, and/or to stick with a 32-bit 
universal build.  There are still a number of rough edges with 64-bit 
builds.

There is perhaps one new wrinkle here: since you didn't specify --with-
universal-archs to configure, configure *thinks* it is building for 32-
bit and defaults to not supplying -arch to the gcc commands it 
generates; on 10.6, though, it looks like the absence of -arch causes a 
64-bit build to take place.  To get around that, configure may need to 
always supply -arch.  Also, I'm guessing that you didn't supply a 
deployment target which results in the somewhat confusing macosx-10.4-
i386 directory names and might have other implications.  (These 
observations are just from a quick look at your build output. This 
should be looked at more thoroughly when time is available.)
History
Date User Action Args
2009-10-22 06:18:52ned.deilysetnosy: + ned.deily, ronaldoussoren
messages: + msg94334

assignee: ronaldoussoren
components: + Macintosh
2009-10-22 00:16:18richardcreate