On Fri, Nov 02, 2018 at 11:29:01PM +0000, Chris Richardson wrote:
> Hi,
Hey Chris,
> I'm getting a build failure after applying any of the most
> recent vserver patches, for instance
> http://vserver.13thfloor.at/Experimental/patch-4.9.135-vs2.3.9.8.diff.
> I've tracked the cause down to the fact that I have IPv6 support
> configured as a module and the vserver code uses statements like
> #if CONFIG_IPV6
> rather than the kernel macro
> #if IS_ENABLED(CONFIG_IPV6)
It is definitely a bug somewhere in the config system as
Linux-VServer should force IPv6 to 'y' or 'n' and disallow
building it as a module.
> I'm wondering if this a bug, or if it perhaps not make
> sense to configure IPv6 as a module in the vserver context?
Building IPv6 as a module is currently not supported by
Linux-VServer, so it doesn't make sense to do that with
the Linux-VServer patches but as I implied, the build
system should take care of this and prevent you from
selecting 'm' in the first place.
I'd appreciate if you could upload (or attach) the .config
you are using so that we can figure out why the build
system doesn't prevent you from building IPv6 as a module.
> Apologies if I'm asking a stupid question, I'm new to vserver!
There are no stupid questions, just stupid answers.
Welcome to Linux-VServer!
Best,
Herbert
> --
> Chris Richardson, System Architect
> cr@fourc.eu
> FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norway
> www.fourc.eu
> Follow us on LinkedIn, Facebook, Google+ and Twitter!
Received on Sat Nov 3 11:04:42 2018