> Cameron Laird wrote: > > ? You might have to go through some of this slowly for me. > > I'm stumbling over the "It will still continue trying to > > build the other extension modules" part. I did "make; make > > install", and no one ever tried to compile Modules/_tkinter.c > > (for example); what am I missing? [MvL] > After setup.py fails to build one extension module, it *should* > continue with the next one. Are you sure _tkinter.sl was not > build??? setup.py skips some modules if the required .h files cannot be found. If you never installed Tcl/Tk, it will skip _tkinter.c silently. For curses, if it can find ncurses.h, it will assume that it can build the curses module. It could be that the ncurses.h found doesn't actually work with _cursesmodule.c; or it could be that the C compiler's search finds a different header file than what setup.py finds (a native C compiler typically has more platform knowledge than distutils). --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4