On Wed, Dec 19, 2012 at 02:28:27AM +0100, Jean-Philippe MENGUAL wrote:
> Actually, according to configure it needs python >= 2.5. Don't get
> > misled by how we record dependencies in the book : what we mean is
> > that we think it will build with the version of Python2 that is in
> > the book.
>
> It seems not. Unless we do some patch, right?
>
> > A quick look at the configure script makes me think you should pass
> > PYTHON=/usr/local/bin/python to configure, NOT PYTHON=2.7
>
> Done. It says yet that "checking if /usr/local/bin/python >=2.5" and no.
> According to configure, 2.7 < 2.5.... I tried with several newer releases of
> glib too, this script says yet "2.7 < 2.5". Very strange!
>
> > The attempt to run python2.5 in configure comes *after* the test
> > for python has failed to find it - at a guess, 2.5 was maybe
> > installed as python2.5 in some circumstance (perhaps if python 1 was
> > present).
>
> 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.
I think that Simon has shown how you can debug what is going wrong.
I'm just replying to clarify a few things:
1. 2.7 is fine for me (in /usr) :
checking for a Python interpreter with version >= 2.5... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/site-packages
2. My comments on dependency versions were aimed more widely - if a
package is not commonly built, it is possible that it doesn't build
with a newer version and nobody will notice for some time. But glib
is *very* commonly built. Because it built fine for me with 2.7, I
didn't include the details in my original reply.
3. The old changelogs show that BLFS has been using Python-2.6.1 or
newer since December 2008. Building 2.5 would not be a good idea.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page