On Wed, Mar 10, 2004 at 02:11:06PM +0000, Chris Withers wrote:
John Poltorak wrote:
I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
What eight lines were they?
See attached diff.
It due to the OS/2 port of Python not being able to handle sticky bits.
Ah, right. What happens if you try 2.7.0?
Configure _appears_ to work OK, but something fails right at the end. Haven't figured out what just yet. This is what happens as it fails:- running build running build_scripts creating U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzeoinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzopeinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/check_catalog.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying utilities/load_site.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/requestprofiler.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/zpasswd.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/testrunner.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/copyzopeskel.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/compilezpy.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/decompilezpy.py -> U:/unixos2/workdir/Zope-2.7.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. "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" \ build --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.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 "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" install \ --home="/opt/Zope-2.7" --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1 Maybe it's a shell problem, I don't know... The invalid command name has me puzzled.
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John