On Fri, Jul 27, 2012 at 12:00 AM, Matthew Garrett <m...@redhat.com> wrote: > We can't assume the presence of the red zone while we're still in a boot > services environment, so we should build with -fno-red-zone to avoid > problems. Change the size of wchar at the same time to make string handling > simpler. > > Signed-off-by: Matthew Garrett <m...@redhat.com> > --- > arch/x86/boot/compressed/Makefile | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/arch/x86/boot/compressed/Makefile > b/arch/x86/boot/compressed/Makefile > index e398bb5..8a84501 100644 > --- a/arch/x86/boot/compressed/Makefile > +++ b/arch/x86/boot/compressed/Makefile > @@ -28,6 +28,9 @@ VMLINUX_OBJS = $(obj)/vmlinux.lds $(obj)/head_$(BITS).o > $(obj)/misc.o \ > $(obj)/string.o $(obj)/cmdline.o $(obj)/early_serial_console.o \ > $(obj)/piggy.o > > +$(obj)/eboot.o: KBUILD_CFLAGS += -fshort-wchar -mno-red-zone > +$(obj)/efi_stub_$(BITS).o: KBUILD_CLFAGS += -fshort-wchar -mno-red-zone > + > ifeq ($(CONFIG_EFI_STUB), y) > VMLINUX_OBJS += $(obj)/eboot.o $(obj)/efi_stub_$(BITS).o > endif
s/CLFAGS/CFLAGS/ should go to stable too? --nX -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
