I tested a nmap-6.49BETA1 build in an isolated build jail (FreeBSD pouderie).
The following configure arg will fail
--with-openssl=/usr --without-localdirs --without-zenmap --without-ndiff --with-libpcre=/usr/local --with-liblua=included --without-nmap-update --prefix=/usr/local
...
checking if AF_INET6 IPPROTO_RAW sockets include the packet header... no
checking for a Python interpreter with version >= 2.4... none
configure: error: in /wrkdirs/usr/ports/security/nmap/work/nmap-6.49BETA1': configure: error: --with-ndiff requires Python 2.x with x>=4 Seeconfig.log' for more details
===> Script "configure" failed unexpectedly.
6.47 builds fine, it seems the culprit comes from the changes in configure.ac to test if python is available and if not ignore --without-ndiff.
I tested a nmap-6.49BETA1 build in an isolated build jail (FreeBSD pouderie).
The following configure arg will fail
--with-openssl=/usr --without-localdirs --without-zenmap --without-ndiff --with-libpcre=/usr/local --with-liblua=included --without-nmap-update --prefix=/usr/local
...
checking if AF_INET6 IPPROTO_RAW sockets include the packet header... no
checking for a Python interpreter with version >= 2.4... none
configure: error: in
/wrkdirs/usr/ports/security/nmap/work/nmap-6.49BETA1': configure: error: --with-ndiff requires Python 2.x with x>=4 Seeconfig.log' for more details===> Script "configure" failed unexpectedly.
6.47 builds fine, it seems the culprit comes from the changes in configure.ac to test if python is available and if not ignore --without-ndiff.