[Zope] Zope startup msgs

John Poltorak jp at warpix.org
Wed Mar 10 09:53:30 EST 2004


On Wed, Mar 10, 2004 at 08:35:17AM -0600, Troy Farrell wrote:
> John Poltorak wrote:
> > 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:-
> > 
> > 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.
> 
> Is it possible that there is a command which consists of only a make variable 
> $(COMMAND) and that variable is empty in this case?


Maybe you can see something untoward in this Makefile that gets created:-



# Zope2 build and install Makefile.

# We do as much as possible in Python in order to avoid needing to
# learn autoconf or some other awful thing. ;-)

NAME=Zope
MAJOR_VERSION=2.7
MINOR_VERSION=0
RELEASE_TAG=b3
PACKAGE_NAME=${NAME}-${MAJOR_VERSION}.${MINOR_VERSION}-${RELEASE_TAG}

PYTHON="U:\USR\BIN\PYTHON.EXE"
TMPDIR=/tmp
PREFIX=/opt/Zope-2.7
BASE_DIR=U:/unixos2/workdir/Zope-2.7.0
BUILD_BASE=U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3
DISTUTILS_OPTS=
INSTALL_FLAGS=
TESTOPTS=-v
BUILD_FLAGS=--build-base="${BUILD_BASE}" \
            --build-lib="${BUILD_BASE}/build-lib" \
            --build-scripts="${BUILD_BASE}/build-scripts"\
            --build-temp="${BUILD_BASE}/build-temp"

RM=rm -f
RMRF=rm -rf
FIND=find
XARGS=xargs
CD=cd
LN=ln -sfn
CP=cp
TAR=tar
MKDIR=mkdir -p

.PHONY : clean install uninstall instance untestinst testinst build 
unbuild
.PHONY : default

# default:     The default step (invoked when make is called without a 
target)
default: build
	@echo
	@echo Zope built.  Next, do \'make install\' \(or \'make instance\'
	@echo to run a Zope instance directly from the build directory\).
	@echo

# build:       Do whatever 'setup.py build' implies
build:
	${PYTHON} "${BASE_DIR}/setup.py" \
           ${DISTUTILS_OPTS} build ${BUILD_FLAGS}

# unbuild:     Remove the build directory (undo the make build step)
unbuild:
	${RMRF} ${BUILD_BASE}

# install:     Install a software home.
#
# Note:  Unless ${PREFIX}/bin already has a 'python', symlink the
#        "canonical" Python for this Zope into it.
install: build
	${PYTHON} "${BASE_DIR}/setup.py" ${DISTUTILS_OPTS} install \
	   --home="${PREFIX}" ${BUILD_FLAGS} ${INSTALL_FLAGS}
	[ -f ${PREFIX}/bin/python ] || ${LN} ${PYTHON} ${PREFIX}/bin/python
	@echo
	@echo Zope binaries installed successfully.
	@echo Now run \'${PREFIX}/bin/mkzopeinstance.py\'




 
> Troy


-- 
John





More information about the Zope mailing list