I'm having problems building v2.7.2 (2.7.0 builds OK) and can't work out exactly where it fails - ie which program is running at the time. I know the Makefile is being processed and suspect it is while making the 'install' target, but it's difficult to pinpoint the place where the error occurs... Here is what I have at the time of the error:- copying and adjusting utilities/decompilezpy.py -> G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-scripts ECHO is on. Zope built. Next, do "\make install\" \(or "\make instance\" to run a Zope instance directly from the build directory\). ECHO is on. "G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" \ build --build-base="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3" --build-lib="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-lib" --build-scripts="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-scripts" --build-temp="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-temp" running build running build_py running build_ext running build running build_py running build running build_scripts "G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" --build-base="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3" --build-lib="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-lib" --build-scripts="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-scripts" --build-temp="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1 I have no idea what this 'invalid command name' is - it doesn't happen with v2.7.0. -- John
--On Mittwoch, 20. Oktober 2004 13:03 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
"G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This looks somewhat weird. You are running a Windows binary PYTHON.exe on a Unix-like filesystem? Please explain! -aj
On Wed, Oct 20, 2004 at 02:07:30PM +0200, Andreas Jung wrote:
--On Mittwoch, 20. Oktober 2004 13:03 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
"G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This looks somewhat weird. You are running a Windows binary PYTHON.exe on a Unix-like filesystem? Please explain!
Actually an OS/2 binary on a Unix-like directory structure... The command has been generated using the supplied configure shell script. It may look weird but works perfectly well - at least with v2.7.0.
-aj
-- John
--On Mittwoch, 20. Oktober 2004 13:15 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
On Wed, Oct 20, 2004 at 02:07:30PM +0200, Andreas Jung wrote:
--On Mittwoch, 20. Oktober 2004 13:03 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
"G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This looks somewhat weird. You are running a Windows binary PYTHON.exe on a Unix-like filesystem? Please explain!
Actually an OS/2 binary on a Unix-like directory structure...
The command has been generated using the supplied configure shell script.
It may look weird but works perfectly well - at least with v2.7.0.
Sorry, no idea about OS/2 (I thought OS/2 died some years ago). Your problem looks a bit like a Distutil problem. -aj
On Wed, Oct 20, 2004 at 02:23:47PM +0200, Andreas Jung wrote:
--On Mittwoch, 20. Oktober 2004 13:15 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
On Wed, Oct 20, 2004 at 02:07:30PM +0200, Andreas Jung wrote:
--On Mittwoch, 20. Oktober 2004 13:03 Uhr +0100 John Poltorak <jp@warpix.org> wrote:
"G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This looks somewhat weird. You are running a Windows binary PYTHON.exe on a Unix-like filesystem? Please explain!
Actually an OS/2 binary on a Unix-like directory structure...
The command has been generated using the supplied configure shell script.
It may look weird but works perfectly well - at least with v2.7.0.
Sorry, no idea about OS/2 (I thought OS/2 died some years ago).
Some things just keep working... It is still available, in fact has just been relaunched by a third party.
Your problem looks a bit like a Distutil problem.
I just tried v2.7.1 and get the same error there. Were there any subtle changes in the build process introduced between 2.7.0 and 2.7.1 ?
-aj
-- John
On Wed, Oct 20, 2004 at 02:19:37PM +0100, John Poltorak wrote:
Your problem looks a bit like a Distutil problem.
I just tried v2.7.1 and get the same error there. Were there any subtle changes in the build process introduced between 2.7.0 and 2.7.1 ?
Big OOOPS! In one instance the MAKESHELL variable was getting set, but not in the other - it makes a big difference. Apologies for timewasting....
-aj
-- John
John Poltorak wrote at 2004-10-20 13:03 +0100:
... running build_scripts "G:\USR\BIN\PYTHON.EXE" "G:/ux2bs/workdir/Zope-2.7.2-0/setup.py" install \ --prefix="/usr/local/Zope" --build-base="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3" --build-lib="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-lib" --build-scripts="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-scripts" --build-temp="G:/ux2bs/workdir/Zope-2.7.2-0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1
Looks like "setup.py" is seeing "" instead of "install" as command. I cannot tell you why -- maybe some weird feature of you shell? Try to call the command directly from the shell. -- Dieter
participants (3)
-
Andreas Jung -
Dieter Maurer -
John Poltorak