From: Andrew Morton <akpm@osdl.org>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Bryce Harrington <bryce@osdl.org>,
linux-kernel@vger.kernel.org, Martin Peschke <mp3@de.ibm.com>
Subject: Re: 2.6.19-rc2-mm2 not building on ia64
Date: Fri, 20 Oct 2006 15:29:39 -0700 [thread overview]
Message-ID: <20061020152939.1af272b4.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0610210007020.29022@twin.jikos.cz>
On Sat, 21 Oct 2006 00:14:34 +0200 (CEST)
Jiri Kosina <jikos@jikos.cz> wrote:
> On Fri, 20 Oct 2006, Bryce Harrington wrote:
>
> > We're seeing the following error building the 2.6.19-rc2-mm2 kernel on
> > ia64 (it builds ok on x86_64). 2.6.19-rc2-git4 builds ok.
> > CC [M] drivers/acpi/processor_throttling.o
> > arch/ia64/sn/kernel/setup.c: In function `sn_setup':
> > arch/ia64/sn/kernel/setup.c:470: error: `ia64_timestamp_clock' undeclared (first use in this function)
> > arch/ia64/sn/kernel/setup.c:470: error: (Each undeclared identifier is reported only once
> > arch/ia64/sn/kernel/setup.c:470: error: for each function it appears in.)
> > CC fs/ext2/namei.o
> > make[2]: *** [arch/ia64/sn/kernel/setup.o] Error 1
> > make[1]: *** [arch/ia64/sn/kernel] Error 2
> > make: *** [arch/ia64/sn] Error 2
> > make: *** Waiting for unfinished jobs....
>
> (added relevant CCs)
>
> This is caused by
> statistics-infrastructure-make-printk_clock-a-generic-kernel-wide-nsec-resolution.patch
>
> I wonder how this could ever compile :)
grr. How many times do we have to tell how many people to not put extern
declarations in C files? This build error is a direct consequence of that
absolutely utterly basic programming mistake.
> Andrew, could you please apply this trivial on top of the original one?
If I had the energy I'd fix it for real, but I don't so I won't. Thanks.
prev parent reply other threads:[~2006-10-20 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 20:57 Bryce Harrington
2006-10-20 22:14 ` Jiri Kosina
2006-10-20 22:29 ` Andrew Morton [this message]
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=20061020152939.1af272b4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bryce@osdl.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mp3@de.ibm.com \
/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
all inboxes | Powered by JetHome®