Hi all,
Has anyone sucessfully compiled python 2.4.2 on centos 4.2 x86_64? I'm trying with soon-to-be fc5 source rpm and it wants to convice me it doesn't know about libX11, but it is there:
#rpmbuild -bb python.spec [snip] gcc -pthread -shared Modules/linuxaudiodev.o -o Modules/linuxaudiodev.so gcc -pthread -shared Modules/timingmodule.o -o Modules/timingmodule.so gcc -pthread -shared Modules/_tkinter.o Modules/tkappinit.o -ltix -ltk -ltcl -lX11 -o Modules/_tkinter.so /usr/bin/ld: cannot find -lX11 collect2: ld returned 1 exit status
but:
# ldconfig -v |grep X11 ldconfig: /usr/X11R6/lib: libX11.so.6 -> libX11.so.6.2 /usr/X11R6/lib64: libX11.so.6 -> libX11.so.6.2
and:
# locate libX11 /usr/X11R6/lib/libX11.so.6 /usr/X11R6/lib/libX11.so.6.2 /usr/X11R6/lib64/libX11.a /usr/X11R6/lib64/libX11.so /usr/X11R6/lib64/libX11.so.6 /usr/X11R6/lib64/libX11.so.6.2
I'm without ideas what's going on here. Anyone?
On 3/19/06, Jure Pečar pegasus@nerv.eu.org wrote:
Hi all,
Has anyone sucessfully compiled python 2.4.2 on centos 4.2 x86_64? I'm trying with soon-to-be fc5 source rpm and it wants to convice me it doesn't know about libX11, but it is there:
Seems people want to go down this hellish road for some reason I have yet to understand.
Messing with python can make your system angry and can affect many other packages like rpm and yum, so proceed with caution and backups.
You can use pyvault if you absolutely need updated python packages, or you may want to consider building in /opt/ so as not to conflict with current system packages. Of the two, I think pyvault may be the safer option, but have backups anyway. Have I stressed the point about backups?
-- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775
On Sun, 19 Mar 2006 17:45:07 -0500 "Jim Perrin" jperrin@gmail.com wrote:
Seems people want to go down this hellish road for some reason I have yet to understand.
I'd avoid it, but client's app demands latest stuff ...
Messing with python can make your system angry and can affect many other packages like rpm and yum, so proceed with caution and backups.
Just define __python_ver to something meaningful, like "24".
You can use pyvault if you absolutely need updated python packages, or you may want to consider building in /opt/ so as not to conflict with current system packages. Of the two, I think pyvault may be the safer option, but have backups anyway. Have I stressed the point about backups?
pyvalut src.rpm barfs even sooner than fedora's.
Anyway, I still don't get why the build process doesn't find libX11, but I found a workaround. The request to link with libX11 comes from python-2.4.1-config.patch, which I modified.
On Sun, 2006-03-19 at 23:51 +0100, Jure Pečar wrote:
On Sun, 19 Mar 2006 17:45:07 -0500 "Jim Perrin" jperrin@gmail.com wrote:
<snip>
Anyway, I still don't get why the build process doesn't find libX11, but I found a workaround. The request to link with libX11 comes from python-2.4.1-config.patch, which I modified.
Do you have "/etc/ld.so.conf" and "/etc/ld.so.conf.d/xorg-x11-i386.conf" popolated properly? If you modified them, did you run "ldconfig" afterwards? "Workarounds" often have later pitfalls.
HTH Bill
On Mon, 20 Mar 2006 08:16:28 -0500 "William L. Maltby" BillsCentOS@triad.rr.com wrote:
Do you have "/etc/ld.so.conf" and "/etc/ld.so.conf.d/xorg-x11-i386.conf" popolated properly? If you modified them, did you run "ldconfig" afterwards? "Workarounds" often have later pitfalls.
Sure I have, I haven't touched them since instalation. ldconfig picks both 32bit and 64bit version of the X11 library ...
-
Jim Perrin -
Jure Pečar -
William L. Maltby