On 05/17/11 03:16, Vasiliy Kulikov wrote: > On Mon, May 16, 2011 at 15:38 -0400, David Miller wrote: >> From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> >> Date: Mon, 16 May 2011 12:35:34 -0700 >> >>> On Mon, 16 May 2011 15:10:19 +1000 Stephen Rothwell wrote: >>> when CONFIG_PROC_SYSCTL is not enabled: >>> >>> ping.c:(.text+0x52af3): undefined reference to `inet_get_ping_group_range_net' >> >> Vasiliy, please fix this. > > I wonder whether there is any way to test such unusual configurations? > Only randconfig or are there any (partly-)automated tools for it? Hi, I do automated (cron) randconfigs nightly and occasionally I run a script that builds a kernel with each one of these options disabled (although lately CONFIG_PM is not being disabled, but I'll fix that one day): BLOCK HOTPLUG INET INPUT MAGIC_SYSRQ NET PCI PM PROC_FS SMP SYSFS Hm, I should add SYSCTL (and/or PROC_SYSCTL) to that list. It often has issues. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
