jump label v7
in [Kernel]
|
Prev: perf: fix initialization bug in parse_single_tracepoint_event()
Next: core: workque: workqueue recursion when unplugging usb WCDMA modem on 2.6.32 kernel
From: David Miller on 22 Apr 2010 19:20 From: Jason Baron <jbaron(a)redhat.com> Date: Fri, 16 Apr 2010 11:24:10 -0400 > David, I re-worked the sparc64 to match the updated interfaces. The > code should hopefully compile now, although I did not test the sparc > bits. Thanks for working on this Jason. I'll take a close look at this some time today. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: David Miller on 27 Apr 2010 21:00 From: David Miller <davem(a)davemloft.net> Date: Thu, 22 Apr 2010 16:17:00 -0700 (PDT) > From: Jason Baron <jbaron(a)redhat.com> > Date: Fri, 16 Apr 2010 11:24:10 -0400 > >> David, I re-worked the sparc64 to match the updated interfaces. The >> code should hopefully compile now, although I did not test the sparc >> bits. > > Thanks for working on this Jason. I'll take a close look at this > some time today. The kernel stops compiling after the second patch because kernel/jump_label.c is compiled unconditionally, and this generates an attempt to include asm/alternatives.h which is an x86-only phenomenon. Do you have access to a cross-compile environment or at least some non-x86 system you can test build on before submitting these patch sets? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Tony Breeds on 27 Apr 2010 21:50 On Tue, Apr 27, 2010 at 05:58:58PM -0700, David Miller wrote: > The kernel stops compiling after the second patch because > kernel/jump_label.c is compiled unconditionally, and this generates an > attempt to include asm/alternatives.h which is an x86-only phenomenon. > > Do you have access to a cross-compile environment or at least some > non-x86 system you can test build on before submitting these patch > sets? I heard cross-compilers? http://kernel.org/pub/tools/crosstool/files/bin/ i686 and x86_64 and 4.4.0 compilers suitable for kernel work. I plan to build 4.4.$latest and 4.5.0 ASAP. Yours Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Mathieu Desnoyers on 27 Apr 2010 22:00 * Tony Breeds (tony(a)bakeyournoodle.com) wrote: > On Tue, Apr 27, 2010 at 05:58:58PM -0700, David Miller wrote: > > > The kernel stops compiling after the second patch because > > kernel/jump_label.c is compiled unconditionally, and this generates an > > attempt to include asm/alternatives.h which is an x86-only phenomenon. > > > > Do you have access to a cross-compile environment or at least some > > non-x86 system you can test build on before submitting these patch > > sets? > > I heard cross-compilers? > > http://kernel.org/pub/tools/crosstool/files/bin/ i686 and x86_64 and 4.4.0 > compilers suitable for kernel work. > > I plan to build 4.4.$latest and 4.5.0 ASAP. > > Yours Tony The crosstool package from Dan Kegel did a good job for this. Not sure it's currently maintained though. It was a very useful project, it's a shame if it does not live on. It would be good to have up-to-date and tested compilers for various architectures available on kernel.org, ideally with access to a package that helps building compilers for various architectures. Thanks, Mathieu -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Tony Breeds on 27 Apr 2010 22:10
On Tue, Apr 27, 2010 at 09:49:41PM -0400, Mathieu Desnoyers wrote: > The crosstool package from Dan Kegel did a good job for this. Not sure > it's currently maintained though. It was a very useful project, it's a > shame if it does not live on. It would be good to have up-to-date and > tested compilers for various architectures available on kernel.org, > ideally with access to a package that helps building compilers for > various architectures. Trimmed the CC' as this is a bit of a tangent. Crosstool did a good job but seems to be less current than we'd like for the kernel[1]. When using crosstool in the past I found a lot of the complexity was in *libc to the toolcahins I've built don';t have a libc so they're only helpful for kernel (or similar) builds. In terms of "testing", I build a kernel for each toolchain but I don't boot them and in the past I think blackfin said that what I had wouldn't actually be runable. Last time I looked the wasn't a non-intel cross-toolchain for blackfin. I shoudl also mention that a subset of these compilers are used to build test linux-next daily. Yours Tony [1] http://www.kegel.com/crosstool/crosstool-0.43/buildlogs/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |