_tkinter fails when installing Python 2.4.4

Diez B. Roggisch deets at nospam.web.de
Wed Mar 26 22:33:56 CET 2008


jgelfand schrieb:
> On Mar 26, 7:02 am, "Diez B. Roggisch" <de... at nospam.web.de> wrote:
>> I think the actual problem is that the linking doesn't find the
>> XftGlyphExtends. I can only guess, but it might be related to
>> 64-bit-problems. Make sure you have the library that contains the
>> XftGlyphExtends is available in the lib64 dirs and so forth.
> 
> I tried running configure with --x-include="/usr/X11R6/include" --x-
> libraries="/usr/X11R6/lib" (in addition to the flags above) and got
> the same error.  I believe XftGlyphExtends is defined in "Xft.h" which
> is located in the directory "/usr/X11R6/include/X11/Xft".  Based on
> the output below, python looks in "/usr/X11R6/include" but not in this
> directory:
> 
> building '_tkinter' extension
> gcc -pthread -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-
> strict-aliasing -DWITH_APPINIT=1 -I/usr/X11R6/include -I. -I/usr/local/
> yosi/Python-2.4.4/./Include -I/usr/local/yosi/ciao-4.0/ots/include -I/
> usr/local/include -I/usr/local/yosi/Python-2.4.4/Include -I/usr/local/
> yosi/Python-2.4.4 -c /usr/local/yosi/Python-2.4.4/Modules/_tkinter.c -
> o build/temp.linux-x86_64-2.4/_tkinter.o
> gcc -pthread -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-
> strict-aliasing -DWITH_APPINIT=1 -I/usr/X11R6/include -I. -I/usr/local/
> yosi/Python-2.4.4/./Include -I/usr/local/yosi/ciao-4.0/ots/include -I/
> usr/local/include -I/usr/local/yosi/Python-2.4.4/Include -I/usr/local/
> yosi/Python-2.4.4 -c /usr/local/yosi/Python-2.4.4/Modules/tkappinit.c -
> o build/temp.linux-x86_64-2.4/tkappinit.o
> gcc -pthread -shared build/temp.linux-x86_64-2.4/_tkinter.o build/
> temp.linux-x86_64-2.4/tkappinit.o -L/usr/X11R6/lib64 -L/usr/X11R6/lib -
> L/usr/local/yosi/ciao-4.0/ots/lib -L/usr/local/lib -ltk8.5 -ltcl8.5 -
> lX11 -o build/lib.linux-x86_64-2.4/_tkinter.so
> 
> When I try setting CFLAGS="-I/usr/X11R6/include/X11/Xft" and re-
> running configure, I get the same error message regardless if I tell
> python to it to use the 32 bit of 64 bit X-Windows libraries.  How
> should I force python to look in this directory?

The above is a LINKER error, not a compiler-error. You need to find the 
library which contains the missing symbol, and trace where it get's 
picked up wrong. Not something (I at least) can do from here.

Diez



More information about the Python-list mailing list