Nmap Development: Re: BHDC08 Version of Nmap/Zenmap

[David Fifield <david () bamsoftware com>]

On Tue, Aug 12, 2008 at 12:23:40PM -0700, Jay Chandler wrote:
> On Aug 12, 2008, at 7:59 AM, David Fifield wrote:
> > Use the PYTHON environment variable when configuring:
> >
> >     PYTHON=/opt/local/bin/python ./configure ...
> >
> > or maybe
> >
> >     PYTHON=/opt/local/bin/python2.5 ./configure ...
> This one is the correct option (as I discovered last night) for the  
> binary location, but then:
>
> checking for /opt/local/bin/python2.5 script directory... ${prefix}/ 
> lib/python2.5/site-packages
> checking for /opt/local/bin/python2.5 extension module directory... $ 
> {exec_prefix}/lib/python2.5/site-packages
>
> How do I assign these as well?
You shouldn't have to. Those messages come from the AM_PATH_PYTHON
Autoconf macro we use to check for Python. We don't use the
PYTHON_PREFIX and PYTHON_EXEC_PREFIX values; those locations are found
out by the setup.py script. It appears you can override PYTHON_PREFIX
and PYTHON_EXEC_PREFIX in the environment but you shouldn't need to.

Try running uninstall_zenmap and reinstalling. distutils (the
distribution system Zenmap uses) doesn't overwrite files on install
unless the file to be installed is newer than the installed file. This
may interfere with other parts of the installation. If that works,
please tell me, and it will be a strong argument for always using
--force when installing Zenmap, which is something I've thought about.

Can you run Zenmap by entering the zenmap source directory and running
"/opt/local/bin/python2.5 zenmap"?

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org