linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Thu, 7 Apr 2005 10:10:26 -0700	[thread overview]
Message-ID: <20050407171026.GO3396@smtp.west.cox.net> (raw)
In-Reply-To: <4240b916050404033230db0551@mail.gmail.com>

On Mon, Apr 04, 2005 at 11:32:39AM +0100, Jerome Glisse wrote:

> Once again i face an error that i got with a previous
> 2.6 kernel (i already posted about this in january
> i think).
[snip]
> Anyway what puzzle me is that it seems i am the
> only one to face this ? Am i alone :) ?

I think you're the only person building a zImage for a 32bit kernel with
a 64bit toolchain for MULTIPLATFORM, yes. :)

This is a valid problem, however.  Does the following also work for you?

Signed-off-by: Tom Rini <trini@kernel.crashing.org>

Index: linux-2.6.10/arch/ppc/boot/simple/Makefile
===================================================================
--- linux-2.6.10.orig/arch/ppc/boot/simple/Makefile
+++ linux-2.6.10/arch/ppc/boot/simple/Makefile
@@ -118,10 +118,13 @@ zimageinitrd-$(pcore)			:= zImage.initrd
          end-$(pcore)			:= pcore
    cacheflag-$(pcore)			:= -include $(clear_L2_L3)
 
+# Really only valid if CONFIG_6xx=y
       zimage-$(CONFIG_PPC_PREP)		:= zImage-PPLUS
 zimageinitrd-$(CONFIG_PPC_PREP)		:= zImage.initrd-PPLUS
+ifeq ($(CONFIG_6xx),y)
      extra.o-$(CONFIG_PPC_PREP)		:= prepmap.o
         misc-$(CONFIG_PPC_PREP)		+= misc-prep.o mpc10x_memory.o
+endif
          end-$(CONFIG_PPC_PREP)		:= prep
 
          end-$(CONFIG_SANDPOINT)	:= sandpoint

-- 
Tom Rini
http://gate.crashing.org/~trini/

  parent reply	other threads:[~2005-04-07 17:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 10:32 linux 2.6.12-rc1-bk5 compilation error Jerome Glisse
2005-04-04 10:51 ` Jerome Glisse
2005-04-04 11:52   ` Jerome Glisse
2005-04-04 12:41 ` Benjamin Herrenschmidt
2005-04-04 19:11   ` Jerome Glisse
2005-04-04 23:12     ` Benjamin Herrenschmidt
2005-04-05 11:52       ` Jerome Glisse
2005-04-05 12:39         ` Andreas Schwab
2005-04-05 15:17           ` Jerome Glisse
2005-04-05 23:12           ` Benjamin Herrenschmidt
2005-04-05 23:25             ` Andreas Schwab
2005-04-05 23:11         ` Benjamin Herrenschmidt
2005-04-07 17:10 ` Tom Rini [this message]
2005-04-08 10:13   ` Jerome Glisse
2005-04-08 15:34     ` [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error) Tom Rini
2005-04-08 22:27       ` Jerome Glisse
2005-04-08 23:47       ` Benjamin Herrenschmidt

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=20050407171026.GO3396@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=j.glisse@gmail.com \
    --cc=linuxppc-dev@ozlabs.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).