On Thursday 2010-09-23 01:23, Mr Dash Four wrote: > >>Yes, it seems to be an unfortunate omission in the Kbuild file. A new release >>will be up shortly, since I have already been pointed towards 2.6.36 changes. > >Oh, it's getting worse! You willingly chose to use Redhat/Fedora. Now endure the pain! :-) >Since the 2 kmod-* and xtabbles-addons rpms do not recognise the custom-built >string after the kernel version - Sounds like another Fedora problem. I know it works in openSUSE, but that is probably because they make sure the custom string is actually _in_ the version (as evidenced by `uname -r`). >A few days ago, I reinstalled[...] > >Guess what? I cannot compile xtables now. I am getting the following error: > > CC libxt_CHAOS.oo > libxt_CHAOS.c:99: warning: implicit declaration of function âALIGNâ > libxt_CHAOS.c:99: error: initializer element is not constant > libxt_CHAOS.c:99: error: (near initialization for âchaos_tg_reg.sizeâ) > libxt_CHAOS.c:100: error: initializer element is not constant > libxt_CHAOS.c:100: error: (near initialization for > âchaos_tg_reg.userspacesizeâ) > make[3]: *** [libxt_CHAOS.oo] Error 1 Yes, someone made a big boo and furthermore did not send the fix to -stable (actually I don't know that), but what I know is that it did not appear in -stable yet. And then there is that 2.6.34 is no longer maintained. Let alone distros mostly don't even think about updating. So everybody using linux-glibc-devel-2.6.34 (that is the userspace package providing /usr/include/linux) is screwed. http://bugs.gentoo.org/show_bug.cgi?id=325257 -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
