[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20061020152939.1af272b4.akpm@osdl.org>
Date: Fri, 20 Oct 2006 15:29:39 -0700
From: Andrew Morton <akpm@...l.org>
To: Jiri Kosina <jikos@...os.cz>
Cc: Bryce Harrington <bryce@...l.org>, linux-kernel@...r.kernel.org,
Martin Peschke <mp3@...ibm.com>
Subject: Re: 2.6.19-rc2-mm2 not building on ia64
On Sat, 21 Oct 2006 00:14:34 +0200 (CEST)
Jiri Kosina <jikos@...os.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists