Joe Conway wrote:
> One procedural issue did occur to me regarding this kind of change.
> It requires someone to run autoconf after applying -- how is that
> normally handled?
You run autoconf before you commit and then check it in. Please use
version 2.53.
--
Peter Eisentraut
http://developer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Conway wrote:
| Gaetano Mendola wrote:
|
|> python -c "from distutils import *" > /dev/null 2>&1 || (echo "You
|> need distutils installed"; exit 1)
|>
|
| Sorry for the delay -- things got busy around here all of a sudden.
|
| Attached is a version
Gaetano Mendola wrote:
python -c "from distutils import *" > /dev/null 2>&1 || (echo "You need
distutils installed"; exit 1)
Sorry for the delay -- things got busy around here all of a sudden.
Attached is a version of the patch with James Pye's distutils checking
code. Gaetano, please verify it
Peter Eisentraut wrote:
Joe Conway wrote:
Perhaps. The first error message seems clear enough to me, but if you
want to send me the necessary distutils test, I can incorporate it.
Any other opinions out there?
It looks like a waste of space and time to me.
Are you serious ? May you quantify the
Joe Conway wrote:
> Perhaps. The first error message seems clear enough to me, but if you
> want to send me the necessary distutils test, I can incorporate it.
> Any other opinions out there?
It looks like a waste of space and time to me. We can't really check
for everything, let alone precondit
Joe Conway wrote:
Gaetano Mendola wrote:
Joe Conway wrote:
I wasn't going to -- python's own docs say I shouldn't need to. From
the link above:
"the Distutils work just fine with Python 1.5.2, and it is reasonable
(and expected to become commonplace) to expect users of Python 1.5.2
to download
On Sat, 2004-09-11 at 14:05, Joe Conway wrote:
> Perhaps. The first error message seems clear enough to me, but if you
> want to send me the necessary distutils test, I can incorporate it. Any
> other opinions out there?
AC_MSG_CHECKING([for Python distutils module])
if "${PYTHON}" 2>&- -c 'impo
Joe Conway wrote:
Gaetano Mendola wrote:
Joe Conway wrote:
What version of python comes with RH2.1?
1.5.2
In any case, the online documentation for python suggests that it is
reasonable to expect that distutils is already installed (by default
for python >= 1.6, and by the user for python 1.5.2)
Gaetano Mendola wrote:
Joe Conway wrote:
I wasn't going to -- python's own docs say I shouldn't need to. From
the link above:
"the Distutils work just fine with Python 1.5.2, and it is reasonable
(and expected to become commonplace) to expect users of Python 1.5.2
to download and install the Di
Gaetano Mendola wrote:
Joe Conway wrote:
What version of python comes with RH2.1?
1.5.2
In any case, the online documentation for python suggests that it is
reasonable to expect that distutils is already installed (by default
for python >= 1.6, and by the user for python 1.5.2). See:
http://www
Joe Conway wrote:
Gaetano Mendola wrote:
Joe Conway wrote:
# python -c "from distutils.sysconfig import get_python_lib as f;
import os; print
os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/config
Any other proposals? If not, any objections to the attached patch?
Gaetano Mendola wrote:
Joe Conway wrote:
# python -c "from distutils.sysconfig import get_python_lib as f;
import os; print
os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/config
Any other proposals? If not, any objections to the attached patch?
No one, we have to
Joe Conway wrote:
James William Pye wrote:
Looking at get_python_lib(), I'm not so sure that I'm correct:
It does seem to work for me:
# python -c "from distutils.sysconfig import get_python_lib as f; import
os; print os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/c
James William Pye wrote:
Looking at get_python_lib(), I'm not so sure that I'm correct:
It does seem to work for me:
# python -c "from distutils.sysconfig import get_python_lib as f; import
os; print os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/config
Any other p
On Thu, 2004-09-09 at 12:28, James William Pye wrote:
> That should work, regardless of the lib directory that Python is
> installed to.
Looking at get_python_lib(), I'm not so sure that I'm correct:
if os.name == "posix":
libpython = os.path.join(prefix,
On Thu, 2004-09-09 at 11:17, Joe Conway wrote:
> On an x86_64 machine I'm finding that I cannot configure --with-python
> without the attached patch. Undoubtedly there is a better way to fix
> this -- any suggestions?
python_configdir=`${PYTHON} -c "from distutils.sysconfig import
get_python_lib
On an x86_64 machine I'm finding that I cannot configure --with-python
without the attached patch. Undoubtedly there is a better way to fix
this -- any suggestions?
Another configure issue: I find that --enable-depend breaks parallel builds:
make -j 2
[...]
make[3]: Entering directory
`/opt/s
17 matches
Mail list logo
