Grammostola Rosea wrote: > Tapani Sysimetsä wrote: > >> Grammostola Rosea wrote: >> >>> Tapani Sysimetsä wrote: >>> >>>> rosea grammostola wrote: >>>> >>>>> We got: >>>>> >>>>> 1. >>>>> /usr/src/compat-wireless-2009-08-24$ sudo make >>>>> 2. >>>>> [sudo] password for marco: >>>>> 3. >>>>> ./scripts/gen-compat-autoconf.sh config.mk <http://config.mk> > >>>>> include/linux/compat_autoconf.h >>>>> 4. >>>>> >>>>> /usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile:41: >>>>> >>>>> >>>>> /usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile_32.cpu: >>>>> >>>>> >>>>> No such file or directory >>>>> 5. >>>>> make[3]: *** No rule to make target >>>>> >>>>> `/usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile_32.cpu'. >>>>> >>>>> >>>>> Stop. >>>>> 6. >>>>> make[2]: *** [sub-make] Error 2 >>>>> 7. >>>>> make[1]: *** [all] Error 2 >>>>> 8. >>>>> ./scripts/gen-compat-autoconf.sh: line 187: [: -le: unary >>>>> operator expected >>>>> 9. >>>>> make -C /lib/modules/2.6.29-1-multimedia-686/build >>>>> M=/usr/src/compat-wireless-2009-08-24 modules >>>>> 10. >>>>> make[1]: Entering directory >>>>> `/usr/src/linux-headers-2.6.29-1-multimedia-686' >>>>> 11. >>>>> >>>>> /usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile:41: >>>>> >>>>> >>>>> /usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile_32.cpu: >>>>> >>>>> >>>>> No such file or directory >>>>> 12. >>>>> make[3]: *** No rule to make target >>>>> >>>>> `/usr/src/linux-headers-2.6.29-1-common-multimedia/arch/x86/Makefile_32.cpu'. >>>>> >>>>> >>>>> Stop. >>>>> 13. >>>>> make[2]: *** [sub-make] Error 2 >>>>> 14. >>>>> make[1]: *** [all] Error 2 >>>>> 15. >>>>> make[1]: Leaving directory >>>>> `/usr/src/linux-headers-2.6.29-1-multimedia-686' >>>>> 16. >>>>> make: *** [modules] Error 2 >>>>> >>>>> >>>>> >>>> Hi, do you have headers-common installed? (from hardy-backports >>>> repository) >>>> >>>> >>> My friend uses the 64studio kernel on Ubuntu jaunty, because >>> installation of 64studio 3 failed. >>> >>> \r >>> >> Ok... I don't know how Jaunty would behave with headers from 64 Studio >> Hardy repos. There is Jaunty backports repo too, but I have never tried. >> deb http://apt.64studio.com/backports/ jaunty-backports main >> >> >> > I can try the headers file from hardy backport on Jaunty right? > And then disable the repo. > > > By the way where is that jaunty-backports coming from? Any experiences with it?
\r _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
