On Tue, 17 Jun 2008, Jan Engelhardt wrote: > >> Be carefull about 32/64 bits architectures, this macro value, perhaps, is > >> diferent depending on it. > > > >No, it holds the same value. > > The same value... currently, and on selected systems ;-) > (UINT_MAX is implementation dependent.) I'm not going to port ipset to other systems. Or do you imply UINT_MAX is implementation dependent on Linux? (Anyway, the successor of ipset is on the way... ;-) > Also, -I/usr/src/linux looks *very* wrong to me, there is reason > we have /usr/include/linux... >From the purists point of you, you are quite right. But ipset (userspace part + kernelspace part) - as it's "based" on patch-o-matic-ng - cannot be compiled without the kernel source. So -I/usr/src/linux is there as a fallback if the kernel source path is not defined explicitely. Best regards, Jozsef - E-mail : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxx PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
