From: Jeff Garzik <jgarzik@pobox.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.9 BK build broken
Date: Mon, 18 Oct 2004 22:32:06 -0400 [thread overview]
Message-ID: <41747CA6.7030400@pobox.com> (raw)
In-Reply-To: <20041019021719.GA22924@merlin.emma.line.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Matthias Andree wrote:
> BitKeeper fails to build (error message with GCC 3.4, ICE with GCC 3.3):
>
> Parent repository is bk://linux.bkbits.net/linux-2.5
> MD5KEY: 417454bfpfdm0m7rr7xnJadPA4ioZA
>
> KEY of latest changeset:
> torvalds@ppc970.osdl.org|ChangeSet|20041018234151|19286
>
> $ LANG=C make CC=/opt/gcc-3.4/bin/gcc
> ...
> LDS arch/i386/kernel/vsyscall.lds
> AS arch/i386/kernel/vsyscall-int80.o
> SYSCALL arch/i386/kernel/vsyscall-int80.so
> AS arch/i386/kernel/vsyscall-sysenter.o
> SYSCALL arch/i386/kernel/vsyscall-sysenter.so
> AS arch/i386/kernel/vsyscall.o
> In file included from include/linux/init.h:5,
> from arch/i386/kernel/vsyscall.S:1:
> include/linux/compiler.h:20: syntax error in macro parameter list
> make[1]: *** [arch/i386/kernel/vsyscall.o] Error 1
> make: *** [arch/i386/kernel] Error 2
I get an ICE here in -BK-latest, which the attached patch fixes (backs
out Linus's change).
I _also_ get a similar failure, in the exact same place, in 2.6.9
[release version] which does _not_ have Linus's change in it. See
http://lkml.org/lkml/2004/10/18/230 for the report.
Maybe the moral of the story is that
linux/init.h + linux/compiler.h + asm == boom ?
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 350 bytes --]
===== include/linux/compiler.h 1.31 vs edited =====
--- 1.31/include/linux/compiler.h 2004-10-18 18:50:37 -04:00
+++ edited/include/linux/compiler.h 2004-10-18 22:26:18 -04:00
@@ -17,7 +17,6 @@
# define __iomem
# define __chk_user_ptr(x) (void)0
# define __chk_io_ptr(x) (void)0
-#define __builtin_warning(x, ...) (1)
#endif
#ifdef __KERNEL__
next prev parent reply other threads:[~2004-10-19 2:32 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 [this message]
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
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=41747CA6.7030400@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=torvalds@osdl.org \
/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