Re: Win32: duplicate _FD_SET symbols?

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 mixter () gmail com wrote:
> Hi,
>
> One more and I hope the last win32 question for now (with some luck).
> So... I just got my (ncat) code back to the stage where all objs compile,
> after some minor adaptions to the VC++2005 -> VC++2008 switch over.
>
> I am again down to the error of duplicate symbols in various obj files,
> essentially the file where I use FD macros clashes with nsock. This
> situation is different than nmap, since nmap outsources all its select()
> relevant stuff right into nsock. Which wouldn't be the right place for
> mine, as it is application specific and used in multiple locations.
>
> If anyone has stumbled over this kind of error, once more, I would greatly
> appreciate any hint.

One set of linking errors seem to be because you have set[] declared in the
ncat.h header and VC++ doesn't like that.  After a quick grep, it seems that
only ncat_proxy.c uses set[], so would it be possible to declare it there
instead?  I may be wrong about this, however, because it's just my first
impression.

I don't know about the _FD_SET macro stuff yet.

I tried building ncat on Linux, but I ran into two problems:

1) The struct fdset_set in ncat.h has two members of type struct fd_set, when
it's really just fd_set.  Some OSs (like I guess Windows) may define it as
something like "typedef struct fd_set { ... } fd_set", but my glibc doesn't.

2) The WSAEWOUDLBLOCK you use in ncat_listen.c isn't inside of a WIN32 ifdef.

These two are no big deal and probably just came about because you've been
working on Windows, but I thought I'd let you know.

> Thanks

Thanks,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBSFSfL/9K37xXYl36AQIqmA/+PEmXbIHBdjZbXRpt2IINNluMFyj7q7Zq
03HZNdV5OUQYa+Dmej2e5LfgcCYQYFK5LzFBz0BVtngma0tswLwZLAYIDWdosLon
hXCB9Mpojy+vkGrbi6rCRfbSWEBzSlxlZU8/rnC6z3aEmo2e+kSOcNLCrCwGryO2
+E8nrYVzAxbeOKHCbxbJX31MACODjAr5TQnQycaHywPUbduqgq7299A7Eqz2Tppr
4tLYJoZiXtwKPF25ISyrYzXtATHSSw+Z+1jWJAFmwDfj2e2p4HAOolM33c81wJlQ
LmmrDjS5jATIGMN8iKqlH5I/xznZ7DH125xgQxTCsj5jusb1zhXYMk23flMxVJTK
jB4E9p+7cEszliVcoMukD1Dt5xod7TI9j+/l5c8qwH0LUAZ829fq8jM4ewqP3uPY
LoZnIzhsTLDd3HXYoZpHS14vVc6jsk7Z3I3FZhWmE+3XDjB9ZrfCEqbJxvZw5TiP
nJP9JpRDXgLIClKh0FhUbAlf84AzPE1YZd1WRGjN3Zk5rYA6yhaDz6eiaU2AErOu
FveRSmBM9RHhN/CGrE8Ch/wpo6kZ3gie8bxdCLvzpqBd7pznYwQMtooByFJcVDMm
9lqUTGYavo5AkAORkes79wh2ncXiSRXNSJWekqtsOs6mwbK1R6ZYm2p1ogrTmZEb
qSxSiHU4efU=
=6Z0V
-----END PGP SIGNATURE-----

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