[mod_python] mod_python & Leopard

On 19/03/2008, Brian <brianlong at cox.net> wrote:
> Graham ::
>
>  Result of make -n
>
>  sh-3.2# make -n
>  if test -z ""; then \
>                 echo; \
>                 echo "Please edit Makefile and set PYTHON_SRC to where Python sources are."; \
>                 echo; \
>                 exit 1; \
>         fi

This could only be the case if you are in the Doc directory when you
run make. Alternatively, your source tree has gotten so screwed up
that the root level Makefile has somehow gotten replaced with that
from the Doc directory.

Does the Makefile in the top level directory contain the following target?

do_dso:
        @cd src && $(MAKE)
        @cd dist && $(MAKE) build
        @echo
        @echo 'Now su and make install'
        @echo '  (or, if you only want to perform a partial install,'
        @echo '   you can use make install_dso and make install_py_lib)'
        @echo

What does the 'all' rule in the makefile say?

I would suggest that you perhaps do a fresh checkout of code from
subversion and start again.

Graham

>  How can I remove the python that is from MacPorts (/Library/....)and/or set the system to use the version of python that came with Leopard (/System/Library....)?
>
>  B
>
>
>
>
>
>  ---- Graham Dumpleton <graham.dumpleton at gmail.com> wrote:
>
> > On 18/03/2008, Brian <brianlong at cox.net> wrote:
>  > > Graham ::
>  > >
>  > >  I thought that I was using the Python that came with the OS, obviously from your comments I am not.  I re-ran configure
>  >
>  > Your previous build lines showed:
>  >
>  >   -I/Library/Frameworks/Python.framework
>  >
>  > For standard OS Python that should be:
>  >
>  >   -I/System/Library/Frameworks/Python.framework
>  >
>  > It would only be the one in /Library/Frameworks if you had MacPorts
>  > Python and it was using that.
>  >
>  > > sh-3.2# make
>  > >
>  > >  Please edit Makefile and set PYTHON_SRC to where Python sources are.
>  >
>  > It doesn't make any sense that you would get that error, as it is
>  > produced from Doc subdirectory and a standard make shouldn't traverse
>  > into that sub directory.
>  >
>  > The only thing I can think is that you have some weird environment
>  > variables set which is causing problems with configure or subsequent
>  > make. I really can't see how changes I made to fix things for MacOS X
>  > Leopard would cause that.
>  >
>  > What is output when you run:
>  >
>  >   make -n
>  >
>  > Graham
>
>