From: Keith M. <kei...@to...> - 2007-03-22 15:12:33
|
OnlyIknow 4sure wrote: > I pasted the configure output and also the change log for Kismet. > This is exactly what I did: > > $ ./configure > . > . > checking sys/socket.h usability... no > checking sys/socket.h presence... no > checking for sys/socket.h... no > configure: error: Missing required system header This much is sufficient, to identify the probable cause of your problem. It looks like Kismet uses UNIX sockets, since the error message seems to relate to the missing `sys/socket.h' file. Your reference to a change log confused me somewhat. I think what you really mean is `config.log', which in this case does no more than confirm the above diagnosis; in its present form, Kismet will not build without UNIX socket support. If you want to build this in MinGW, then you'll need to port it, so it uses Windows sockets instead. This has been discussed a number of times previously, (some quite recently); please search the archives. Regards, Keith. |