On Wed, 2012-12-19 at 02:28 +0100, Jean-Philippe MENGUAL wrote: > I guess installing python 2.5 without any instructions isn't so easy. > Moreover, it's strange that configure sees python 2.7 < 2.5. I think > either this package should be patched, or the dependency in the book > should be python2.5 with a link to instructions for python2.5.
Ok, so looking at the glib configure script, it's running the following
fragment to determine the Python version. What happens if you try
running the following from a Bash shell?
/usr/local/bin/python << "EOF"
import sys
minver = list(map(int, '2.5'.split('.'))) + [0, 0, 0]
minverhex = 0
for i in list(range(0, 4)):
minverhex = (minverhex << 8) + minver[i]
print (sys.hexversion < minverhex)
EOF
Basically, it's turning the minimum version 2.5 into a hexadecimal
representation, and comparing it against Python's declared version. If
you have Python 2.7 installed, it should print out "False" (meaning the
version it's found isn't too old).
You could also try:
/usr/local/bin/python << "EOF"
import sys
print hex(sys.version)
EOF
...to get a more human-readable encoding of that version number, e.g I
get 0x20703f0 (2.7.3.x) on the Fedora box I'm on right now...
Also, try reading the config.log file produced by the glib build, and
see if there's any obvious reason for it rejecting your Python
installation.
Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
