public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 BK build broken
Date: Mon, 18 Oct 2004 22:10:41 -0700	[thread overview]
Message-ID: <20041018221041.184632cb.akpm@osdl.org> (raw)
In-Reply-To: <20041019021719.GA22924@merlin.emma.line.org>

Matthias Andree <matthias.andree@gmx.de> wrote:
>
> include/linux/compiler.h:20: syntax error in macro parameter list

I used this:



include/linux/compiler.h:20: syntax error in macro parameter list

It fails because we use -traditional when compiling .S files.

Signed-off-by: Andrew Morton <akpm@osdl.org>
---

 25-akpm/include/linux/compiler.h |    4 +++-
 1 files changed, 3 insertions(+), 1 deletion(-)

diff -puN include/linux/compiler.h~builtin_warning-is-not-traditional include/linux/compiler.h
--- 25/include/linux/compiler.h~builtin_warning-is-not-traditional	2004-10-18 22:08:25.224796488 -0700
+++ 25-akpm/include/linux/compiler.h	2004-10-18 22:09:05.505672864 -0700
@@ -17,7 +17,9 @@ extern void __chk_io_ptr(void __iomem *)
 # define __iomem
 # define __chk_user_ptr(x) (void)0
 # define __chk_io_ptr(x) (void)0
-#define __builtin_warning(x, ...) (1)
+#ifndef __ASSEMBLY__	/* gcc -traditional fails with varargs-style macros */
+# define __builtin_warning(x, ...) (1)
+#endif
 #endif
 
 #ifdef __KERNEL__
_


  parent reply	other threads:[~2004-10-19  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19  2:17 2.6.9 BK build broken Matthias Andree
2004-10-19  2:32 ` Jeff Garzik
2004-10-19  3:32   ` Jeff Garzik
2004-10-19  5:14     ` Linus Torvalds
2004-10-19  9:00       ` Matthias Andree
2004-10-19 16:05         ` Linus Torvalds
2004-10-19  9:23       ` SOLVED: " Matthias Andree
2004-10-19  5:10 ` Andrew Morton [this message]
2004-10-19  9:03   ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041018221041.184632cb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox