From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc3-mm2 (build failure on arm)
Date: Wed, 28 Nov 2007 11:54:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711281152220.12651@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071128034140.648383f0.akpm@linux-foundation.org>
Crossbuild on arm with shark_deconfig fails:
CC [M] sound/oss/uart401.o
CC net/sched/sch_generic.o
CC net/core/dst.o
AS arch/arm/lib/getuser.o
drivers/ide/arm/ide_arm.c: In function 'ide_arm_init':
drivers/ide/arm/ide_arm.c:42: error: implicit declaration of function
'ide_device_idx'
make[2]: *** [drivers/ide/arm/ide_arm.o] Error 1
make[1]: *** [drivers/ide] Error 2
make[1]: *** Waiting for unfinished jobs....
CC net/core/netevent.o
CC net/core/neighbour.o
next prev parent reply other threads:[~2007-11-28 19:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 11:41 2.6.24-rc3-mm2 Andrew Morton
2007-11-28 12:40 ` 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared Kamalesh Babulal
2007-11-28 13:32 ` Arnd Bergmann
2007-11-28 18:43 ` Andrew Morton
2007-11-28 19:25 ` Davide Libenzi
2007-11-29 0:57 ` Arnd Bergmann
2007-11-28 13:07 ` 2.6.24-rc3-mm2 Build Failure at imacfb framebuffer driver Kamalesh Babulal
2007-11-28 18:51 ` Andrew Morton
2007-11-28 14:16 ` 2.6.24-rc3-mm2 Boaz Harrosh
2007-11-28 14:22 ` [PATCH] 2.6.24-rc3-mm2 build failure pasemi-rng driver Kamalesh Babulal
2007-12-01 19:32 ` Olof Johansson
2007-11-28 14:33 ` [BUG] 2.6.24-rc3-mm2 soft lockup while running tbench Kamalesh Babulal
2007-11-29 21:09 ` Andrew Morton
2007-11-30 5:09 ` Kamalesh Babulal
2007-11-28 19:52 ` 2.6.24-rc3-mm2 (build failure on s390) Christoph Lameter
2007-11-28 20:03 ` Andrew Morton
2007-11-28 19:54 ` Christoph Lameter [this message]
2007-11-28 20:06 ` 2.6.24-rc3-mm2 (build failure on arm) Andrew Morton
2007-11-28 20:33 ` Bartlomiej Zolnierkiewicz
2007-11-28 20:01 ` 2.6.24-rc3-mm2: Result: hostbyte=0x01 driverbyte=0x00\nend_request: I/O error Alexey Dobriyan
2007-11-28 21:40 ` Andrew Morton
2007-11-28 22:12 ` Alan Cox
2007-11-28 23:14 ` Matthew Wilcox
2007-11-28 23:36 ` Andrew Morton
2007-11-29 9:33 ` Boaz Harrosh
2007-11-28 22:05 ` 2.6.24-rc3-mm2 - *not* an insta-brick on my Latitude Valdis.Kletnieks
2007-11-28 23:06 ` named + capset = EPERM [Was: 2.6.24-rc3-mm2] Jiri Slaby
2007-11-28 23:31 ` Casey Schaufler
2007-11-28 23:47 ` Serge E. Hallyn
2007-11-29 0:04 ` Serge E. Hallyn
2007-11-29 0:17 ` Serge E. Hallyn
2007-11-29 22:56 ` Jiri Slaby
2007-11-29 3:23 ` 2.6.24-rc3-mm2 KAMEZAWA Hiroyuki
2007-11-29 5:24 ` 2.6.24-rc3-mm2 (bugfix for memory cgroup per-zone-struct allocation.) KAMEZAWA Hiroyuki
2007-11-29 21:25 ` Lee Schermerhorn
2007-11-30 0:14 ` KAMEZAWA Hiroyuki
2007-11-29 9:00 ` [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions Kamalesh Babulal
2007-11-29 9:09 ` Andrew Morton
2007-11-29 11:57 ` Kamalesh Babulal
2007-11-29 12:10 ` Jan Kara
2007-11-29 14:36 ` Kamalesh Babulal
2007-11-29 14:40 ` Jan Kara
2007-12-02 15:55 ` Kamalesh Babulal
2007-11-29 20:58 ` 2.6.24-rc3-mm2 Torsten Kaiser
2007-11-29 21:07 ` 2.6.24-rc3-mm2 Andrew Morton
2007-11-29 22:30 ` 2.6.24-rc3-mm2 Stefan Richter
2007-12-03 20:27 ` 2.6.24-rc3-mm2 Torsten Kaiser
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=Pine.LNX.4.64.0711281152220.12651@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).