On 03/13/2012 10:50 AM, Jan Stancek wrote: > Hi, > > I hit the same issue couple days back with RHEL. > All that was needed for 2.6.14 is: > > --- Makefile 2005-10-27 20:02:08.000000000 -0400 > +++ Makefile.orig 2012-03-08 09:36:27.506290505 -0500 > @@ -447,7 +447,11 @@ > include $(srctree)/arch/$(ARCH)/Makefile > export KBUILD_DEFCONFIG > > -config %config: scripts_basic outputmakefile FORCE > +config: scripts_basic outputmakefile FORCE > + $(Q)mkdir -p include/linux > + $(Q)$(MAKE) $(build)=scripts/kconfig $@ > + > +%config: scripts_basic outputmakefile FORCE > $(Q)mkdir -p include/linux > $(Q)$(MAKE) $(build)=scripts/kconfig $@ > > 2.6.18 and 2.6.20 have similar issues, but with patches similar to one above > I could build it on x86_64, ppc64 and s390x.
Hi Jan, Would it be possible to verify whether my upgrade to 3.2 patch works smoothly on your use cases? I did upgrade because 2.6.14 was getting way too old, and for upstream it'd make sense to track new kernel releases... Thanks! _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
