From: Tom Rini <trini@kernel.crashing.org>
To: Hal <pshbro@open.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: missing config options in 2.6.0-test5-bk1 arch PPC
Date: Fri, 12 Sep 2003 08:01:04 -0700 [thread overview]
Message-ID: <20030912150104.GD13672@ip68-0-152-218.tc.ph.cox.net> (raw)
In-Reply-To: <3F5A001F.10509@open.org>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Sat, Sep 06, 2003 at 08:41:19AM -0700, Hal wrote:
> [1] arch/ppc/platforms/mpc82xx.h: platforms/willow.h not found.
>
> [2]
>
> In arch/ppc/platforms/mpc82xx.h line 33 platforms/willow.h is included.
> This file does not exist.
>
> [3] arch/ppc/kernel/asm-offsets.s include/asm/io.h include/asm/mpc8260.h
> platforms/willow.h
>
> [4] 2.6.0-test5-bk1
>
> [5]
>
> CC arch/ppc/kernel/asm-offsets.s
> In file included from include/asm/mpc8260.h:12,
> from include/asm/io.h:32,
> from arch/ppc/kernel/asm-offsets.c:21:
> arch/ppc/platforms/mpc82xx.h:33:30: platforms/willow.h: No such file
> or directory
> make[1]: *** [arch/ppc/kernel/asm-offsets.s] Error 1
> make: *** [arch/ppc/kernel/asm-offsets.s] Error 2
>
> [6] make allyesconfig; make
The notion of 'allyesconfig' is broken on PPC, IMHO. If you want to try
test compiling a number of drivers, do this, followed by whichever
config target you normally do, and build for a pmac, or whatever
hardware you actually have.
--
Tom Rini
http://gate.crashing.org/~trini/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-09-12 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 15:41 BUG: missing config options in 2.6.0-test5-bk1 arch PPC Hal
2003-09-12 15:01 ` Tom Rini [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=20030912150104.GD13672@ip68-0-152-218.tc.ph.cox.net \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pshbro@open.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).