On 07/19/2010 02:41 PM, Eric Blake wrote: > [adding gnulib] > > On 07/04/2010 07:51 PM, Philip Prindeville wrote: >>> Generally, for such issues it might be a good idea to just use gnulib if >>> you can; but I just looked and it doesn't address this particular issue >>> yet. >>> >>> Cheers, >>> Ralf >>> >> >> Ok, slightly different issue. >> >> I'm trying to test for the presence/usability of <netinet/ip.h>, but on >> certain platforms I need to include <netinet/insystm.h> first. >> >> configure:21873: checking netinet/ip.h usability >> configure:21873: gcc -c -g -O2 conftest.c>&5 >> In file included from conftest.c:155: >> /usr/include/netinet/ip.h:67: error: field `ip_src' has incomplete type >> /usr/include/netinet/ip.h:67: error: field `ip_dst' has incomplete type >> /usr/include/netinet/ip.h:160: error: syntax error before "n_long" >> /usr/include/netinet/ip.h:162: error: field `ipt_addr' has incomplete type >> /usr/include/netinet/ip.h:163: error: syntax error before "n_long" >> /usr/include/netinet/ip.h:198: error: field `ippseudo_src' has >> incomplete type >> /usr/include/netinet/ip.h:199: error: field `ippseudo_dst' has >> incomplete type > > Which platform? Again, using gnulib might be the cleanest way to not > have to worry about this; and in the meantime, gnulib probably needs to > be updated to deal with your particular platform with an incomplete header. >From what I can tell (the automated build infrastructure has a few kinks, and I don't always get accurate or full build logs)... both OpenBSD and Solaris (or OpenSolaris). I use autoconf in many more environments than I use gnulib. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
