Nmap Development mailing list archives

RE: [Patch] Port and Host State Reasons


From: "Thomas Buchanan" <TBuchanan () thecompassgrp net>
Date: Fri, 18 May 2007 16:56:40 -0500

-----Original Message-----
From: nmap-dev-bounces () insecure org 
[mailto:nmap-dev-bounces () insecure org] On Behalf Of Eddie Bell
Sent: Friday, May 18, 2007 7:44 AM
To: nmap-dev () insecure org
Subject: Re: [Patch] Port and Host State Reasons

<snip>

The updated code is available in SVN at /nmap-exp/ejlbell along with
my previous traceroute update

Thanks for testing it
 - eddie



Eddie,

I was trying to build your SVN branch on Windows, using Visual C++ 2005
Express, and I'm running into a couple of build issues that I don't see
on the main branch.

The first is that apparently the MS compiler does not like the
overloaded function definitions in the include file "reason.h".  I end
up with a lot of these messages:

..\reason.h(167) : error C2733: second C linkage of overloaded function
'reason_str' not allowed
..\reason.h(167) : see declaration of 'reason_str'

That error I can fix by commenting out one of the two definitions, but
then I'm still left with a lot of errors regarding the include file
<netinet/ip.h>.  These I'm not sure how to fix:

.\netinet/ip.h(148) : error C2146: syntax error : missing ';' before
identifier 'ipt_time'
.\netinet/ip.h(148) : error C4430: missing type specifier - int assumed.
Note: C++ does not support default-int
.\netinet/ip.h(148) : error C4430: missing type specifier - int assumed.
Note: C++ does not support default-int
.\netinet/ip.h(151) : error C2146: syntax error : missing ';' before
identifier 'ipt_time'
.\netinet/ip.h(151) : error C4430: missing type specifier - int assumed.
Note: C++ does not support default-int
.\netinet/ip.h(151) : error C4430: missing type specifier - int assumed.
Note: C++ does not support default-int

These errors are not present in the build of the main SVN branch, but I
don't see any difference in that file between your branch and HEAD.

Not sure if you do any of your development on Windows, but if anyone has
ideas on how to get around this, I'd be happy to try them.

Thanks,

Thomas

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


Current thread: