Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761489AbXJYPcp (ORCPT ); Thu, 25 Oct 2007 11:32:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751001AbXJYPce (ORCPT ); Thu, 25 Oct 2007 11:32:34 -0400 Received: from mx1.redhat.com ([66.187.233.31]:41062 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752706AbXJYPcd (ORCPT ); Thu, 25 Oct 2007 11:32:33 -0400 From: Glauber de Oliveira Costa To: linux-kernel@vger.kernel.org Cc: akpm@linux-foundation.org, Jeremy Fitzhardinge , glommer@gmail.com, Glauber de Oliveira Costa Subject: [PATCH] Wipe out traditional opt from x86_64 Makefile Date: Thu, 25 Oct 2007 09:47:52 -0300 Message-Id: <11933164723812-git-send-email-gcosta@redhat.com> X-Mailer: git-send-email 1.4.4.2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1213 Lines: 34 Among other things, using -traditional as a gcc option stops us from using macro token pasting, which is a feature we heavily rely on. There was still a use of -traditional in arch/x86/kernel/Makefile_64, which this patch removes. I don't see any problems building kernels in my x86_64 box without -traditional. Signed-off-by: Glauber de Oliveira Costa --- arch/x86/kernel/Makefile_64 | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/arch/x86/kernel/Makefile_64 b/arch/x86/kernel/Makefile_64 index 82da906..03a01f6 100644 --- a/arch/x86/kernel/Makefile_64 +++ b/arch/x86/kernel/Makefile_64 @@ -3,7 +3,6 @@ # extra-y := head_64.o head64.o init_task.o vmlinux.lds -#EXTRA_AFLAGS := -traditional obj-y := process_64.o signal_64.o entry_64.o traps_64.o irq_64.o \ ptrace_64.o time_64.o ioport_64.o ldt_64.o setup_64.o i8259_64.o sys_x86_64.o \ x8664_ksyms_64.o i387_64.o syscall_64.o vsyscall_64.o \ -- 1.4.4.2 - 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/