Messages in this thread | | | Date | Thu, 24 Mar 2011 09:06:08 +0100 | Subject | Re: [PATCH 0/1] m68k: merge m68k and m68knommu arch directories | From | Geert Uytterhoeven <> |
| |
Hi Greg,
On Thu, Mar 24, 2011 at 00:00, Greg Ungerer <gerg@snapgear.com> wrote: > On 24/03/11 08:07, Geert Uytterhoeven wrote: >> On Tue, Mar 22, 2011 at 05:43,<gerg@snapgear.com> wrote: >>> slso on the for-next branch in that tree, so will get some testing >>> in the next tree for the next few days. >> >> defconfig is now a nommu-config, and it fails? >> >> http://kisskb.ellerman.id.au/kisskb/buildresult/4012794/ > > Yep, that looks wrong. I'll move the define for KBUILD_DEFCONFIG > into arch/m68k/Makefile (and remove the existing defines in Makefile_mm > and Makefile_no). That will make the DEFCONFIG as it was before, > multi_defconfig. > >> arch/m68k/kernel/entry_no.S:47: Error: Unknown operator -- statement >> `save_all' ignored > > This is due to compiling for the non-mmu targets and not using > a m68k-uclinux- toolchain. Unfortunately the compiler must define > __uClinux__ to compile for non-mmu targets. This isn't new, we
For userland...
> have had this problem ever since the merge of the header files. > (The exported headers need some switch to use to base some > conditionals on, and kernel config options cannot be used in > exported headers).
For kernels, we can explicitly define this in arch/m68k/Makefile if !MMU, right?
> But with a fixed defconfig, you won't see this anymore :-) > > I'll fix up the git commit on m68knommu git tree.
Good, thx!
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |