From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 CONFIG_BOOT_LOAD undefined
Date: Thu, 14 Aug 2003 19:44:06 +0200 [thread overview]
Message-ID: <20030814174406.GB5270@suse.de> (raw)
In-Reply-To: <20030814165403.GT807@ip68-0-152-218.tc.ph.cox.net>
On Thu, Aug 14, Tom Rini wrote:
> The problem is that PPC_MULTIPLATFORM does not go into
> arch/ppc/boot/simple/, except for one file. The log you posted shows it
> trying to link a zvmlinuz in there.
>
> By chance do all of your tools meet the requirements in
> Documentation/Changes ? Assuming that's been kept up to date.
Yes, it is uptodate, SuSE 8.2.
I found that it goes into /simple/ only once, and that fails.
208 cp -av .config ../config.foo
209 make distclean
210 l
211 cp ../config.foo .config
212 /usr/bin/time make oldconfig zImage modules modules_install INSTALL_MOD_PATH=`pwd` &>log
fails
213 w
214 o log
215 make zImage
succeeds
216 rm -fv arch/ppc/boot/simple/*.o
217 make zImage
succeeds
218 history
That makes we wonder, 'make oldconfig zImage' is different from 'make zImage'?
Must be some dependency problem.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-14 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 7:51 linuxppc-2.5 CONFIG_BOOT_LOAD undefined Olaf Hering
2003-08-13 23:35 ` Tom Rini
2003-08-14 10:39 ` Olaf Hering
2003-08-14 16:05 ` Tom Rini
2003-08-14 16:45 ` Olaf Hering
2003-08-14 16:54 ` Tom Rini
2003-08-14 17:44 ` Olaf Hering [this message]
2003-08-14 18:43 ` Tom Rini
2003-08-14 19:31 ` Sam Ravnborg
2003-08-14 19:34 ` Olaf Hering
2003-08-14 21:02 ` Sam Ravnborg
2003-08-16 7:49 ` Sam Ravnborg
2003-08-16 11:41 ` Olaf Hering
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=20030814174406.GB5270@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.