I've got this as well, and I think we can just ignore this (for now). The reason of the warning was because we need to include <windows.h> before including <mswsock.h>. cheers, -benny Klaus Darilion wrote: > Forgot to mention: This happened during ./aconfigure on WindowsXP unsing > MSYS (from MinGW). > > regards > klaus > > Klaus Darilion wrote: >> checking for time.h... yes >> checking for unistd.h... (cached) yes >> checking mswsock.h usability... no >> checking mswsock.h presence... yes >> aconfigure: WARNING: mswsock.h: present but cannot be compiled >> aconfigure: WARNING: mswsock.h: check for missing prerequisite headers? >> aconfigure: WARNING: mswsock.h: see the Autoconf documentation >> aconfigure: WARNING: mswsock.h: section "Present But Cannot Be Compiled" >> aconfigure: WARNING: mswsock.h: proceeding with the preprocessor's result >> aconfigure: WARNING: mswsock.h: in the future, the compiler will take >> precedence >> aconfigure: WARNING: ## ------------------------------------ ## >> aconfigure: WARNING: ## Report this to the pjproject lists. ## >> aconfigure: WARNING: ## ------------------------------------ ## >> checking for mswsock.h... yes >> checking winsock.h usability... yes >> checking winsock.h presence... yes >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -- Benny Prijono http://www.pjsip.org
