Nmap Development mailing list archives

Re: Nmap 4.75 Posted!


From: David Fifield <david () bamsoftware com>
Date: Mon, 8 Sep 2008 10:39:51 -0600

On Mon, Sep 08, 2008 at 09:50:38AM +0200, Lionel Cons wrote:
Fyodor writes:
 > Please give it a try and report any problems, [...]

It fails to compile on my machine (a Red Hat Enterprise Linux 4
derivative). Previous versions compiled fine.

I'm using SVN revision 10026 and get:

make[1]: Entering directory `/tmp/BUILD/nbase'
autoconf
configure.ac:108: error: possibly undefined macro: AC_TYPE_INT8_T
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:109: error: possibly undefined macro: AC_TYPE_INT16_T
configure.ac:110: error: possibly undefined macro: AC_TYPE_INT32_T
configure.ac:111: error: possibly undefined macro: AC_TYPE_INT64_T
configure.ac:112: error: possibly undefined macro: AC_TYPE_UINT8_T
configure.ac:113: error: possibly undefined macro: AC_TYPE_UINT16_T
configure.ac:114: error: possibly undefined macro: AC_TYPE_UINT32_T
configure.ac:115: error: possibly undefined macro: AC_TYPE_UINT64_T
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/tmp/BUILD/nbase'
make: *** [nbase_build] Error 2

The nbase makefile is re-running autoconf because it thinks configure is
out of date. Somehow configure must be older than configure.ac. I'm
fuzzy on how Subversion handles modification dates but it seems this has
happened once or twice before.

A workaround is to run "touch nbase/configure" to bring the configure
script up to date. You may need to run "svn revert -R nbase" first to
get rid of any changes the failed autoconf run may have made.

The AC_TYPE_*_T macros were added in Autoconf 2.59c in 2006, so whatever
Autoconf is installed must be older than that. My guess is that this is
a one-time problem caused by file modifications times being changed by a
recent Subversion update. Does it happen with a fresh checkout?

David Fifield

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


Current thread: