From: Owen C. <oc...@cs...> - 2002-08-01 14:47:04
|
I had a bit of trouble configuring from CVS, couple of observations. * The CVS configure script seems to depend on libtool 1.4.2 (doesn't work with 1.4) if this is the case, having that in the README might save some people some time :) * The Python tests don't check for the the existence of python2 (just uses python) the Python.org RPMS install python 2.x as python2 for compatibility. RPMS install python 2.x as python2 for compatibility. i presume this might be a problem in the Python autoconf scripts though? * The configure script doesn't seem to detect gnome-python 1.99.20 (says it is looking for pygnome. owen |
From: Arjan M. <arj...@he...> - 2002-08-02 07:32:19
|
On Wed, 2002-07-31 at 16:19, Owen Cliffe wrote: > I had a bit of trouble configuring from CVS, couple of observations. > > * The CVS configure script seems to depend on libtool 1.4.2 (doesn't > work with 1.4) if this is the case, having that in the README might save > some people some time :) didn't know that. I'll fix it, thanks. > * The Python tests don't check for the the existence of python2 (just > uses python) the Python.org RPMS install python 2.x as python2 for > compatibility. RPMS install python 2.x as python2 for compatibility. i > presume this might be a problem in the Python autoconf scripts though? This is indeed an autoconf thing. It does check up to version 2.1 (python, python2.1, python2.0, python1.6, python1.5, in that order). You should also have that problem if you compile PyGTK. > * The configure script doesn't seem to detect gnome-python 1.99.20 (says > it is looking for pygnome. Typo. fixed. Thanks for pointing it out. I'll work on it. Regards, Arjan |
From: Arjan M. <arj...@he...> - 2002-08-05 09:27:13
|
On Fri, 2002-08-02 at 09:33, Arjan Molenaar wrote: > On Wed, 2002-07-31 at 16:19, Owen Cliffe wrote: > > I had a bit of trouble configuring from CVS, couple of observations. > > > > * The CVS configure script seems to depend on libtool 1.4.2 (doesn't > > work with 1.4) if this is the case, having that in the README might save > > some people some time :) > > didn't know that. I'll fix it, thanks. > > > * The Python tests don't check for the the existence of python2 (just > > uses python) the Python.org RPMS install python 2.x as python2 for > > compatibility. RPMS install python 2.x as python2 for compatibility. i > > presume this might be a problem in the Python autoconf scripts though? > > This is indeed an autoconf thing. It does check up to version 2.1 > (python, python2.1, python2.0, python1.6, python1.5, in that order). > > You should also have that problem if you compile PyGTK. It should work now. I've created a custom macro for detecting Python. It checks python2.2, python2 and at last it checks python. That should do the trick... Regards, Arjan |