On Thu, Jan 11, 2007 at 05:24:40PM +0100, Radek Vokál wrote:
> Thomas Anders wrote:
> >Radek Vokál wrote:
> >>Hi, I can't figure out where the problem. Net-snmp doesn't configure 
> >>with ethtool because the following test crashes
> >>
> >>configure:20372: checking for linux/ethtool.h
> >>configure:20394: gcc -c -DINET6 -O2 -g -pipe -Wall 
> >>-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> >>--param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic 
> >>-fasynchronous-unwind-tables -lcrypto -Dlinux -I/usr/include/rpm 
> >>-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe 
> >>-Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE 
> >>-D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm 
> >>-I/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE  conftest.c >&5
> >>In file included from conftest.c:134:
> >>/usr/include/linux/ethtool.h:18: error: expected 
> >>specifier-qualifier-list before '__u32'
> >
> >net-snmp version? OS version? configure options?
> >
> >
> >+Thomas
> >
> 
> I'm sending you a patch which fixies the issue for me. This is Fedora 
> Core 6 and RHEL5 issue. Net-snmp 5.3.1 and 5.4

I am against this patch since it breaks with not-so-old linux versions.

The relevant change in the linux kernel code happened between 2.6.17 and 2.6.18
so this is way out.

The other thing is that the following might be an outline that works with both
versions.

AC_CHECK_HEADERS([linux/types.h])
AC_CHECK_HEADERS([linux/eth_tool.h],[],[],[
#ifdef HAVE_LINUX_TYPES_H
#include <linux/types.h>
#endif])

/MF

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to