Building against external libdnet (was: Build Nmap-5.00 without sctp support)

[Daniel Roethlisberger <daniel () roe ch>]

Giovanni Bechis <bigionews () snb it> 2009-07-27:
> David Fifield wrote:
> > Hello. There should be no need to port Nmap to OpenBSD. If it takes
> > special work to make it compile or run then it's a bug, so please submit
> > a patch so that we can integrate it with the mainline code.
> We added a sctp.h file to the source to let nmap build (otherwise nmap 
> cannot find a few structs)

You are trying to build against an external libdnet from OpenBSD
ports, right?  To do so, you'd need to update the libdnet port to
latest libdnet trunk [1] or use Nmap's internal libdnet.  Dug
Song so far hasn't released a libdnet release including my SCTP
extensions.

[1] http://code.google.com/p/libdnet/

However, since the Nmap internal libdnet has a lot of patches
which have not been merged to upstream libdnet, using external
libdnet is not such a terribly good idea anyway.  Users of the
OpenBSD port will miss out on many small bugfixes and
Nmap-specific improvements to libdnet.  You could of course add
patches containing all the libdnet additions in Nmap's
libdnet-stripped to the libdnet port.  Beware that many of these
are untested outside of Nmap.

Actually, I'd suggest we remove or disable the ./configure option
to build Nmap against an external libdnet as long as the list of
unmerged patches is as long as it is currently.  It's not just
the SCTP stuff which is missing in external libdnet versions.  Or
at least add a warning to the description of the option in
./configure --help.  Opinions?

-- 
Daniel Roethlisberger
http://daniel.roe.ch/

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