linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven@powerlinux.fr>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Bernhard Reiter <bernhard@intevation.de>,
	debian-powerpc@lists.debian.org, paulus@samba.org
Subject: Re: compile quirk linux-2.6.24 (with workaround)
Date: Tue, 5 Feb 2008 15:39:26 +0100	[thread overview]
Message-ID: <20080205143926.GA9709@powerlinux.fr> (raw)
In-Reply-To: <20080205070833.3a5b7c11@zod.rchland.ibm.com>

On Tue, Feb 05, 2008 at 07:08:33AM -0600, Josh Boyer wrote:
> On Mon, 4 Feb 2008 10:51:21 +0100
> Sven Luther <sven@powerlinux.fr> wrote:
> 
> > On Sun, Feb 03, 2008 at 05:29:05PM +0100, Bernhard Reiter wrote:
> > > Dear linux powerpc Maintainers and Users,
> > > 
> > > recently I have tried to compile a new kernel on a Debian sarge ppc
> > > system (PowerBook5,6 MacRISC3 Power Macintosh).
> > 
> > This is a G4 based system.
> > 
> > > The build system bailed out with
> > >        BOOTCC  arch/powerpc/boot/4xx.o
> > >         cc1: error: bad value (440) for -mcpu= switch
> > >         make[1]: *** [arch/powerpc/boot/4xx.o] Fehler 1
> > > 
> > > I have tracked this a few steps and the attached patch made the compile for me
> > > as my compiler gcc-Version 3.3.5 (Debian 1:3.3.5-13) 
> > > cannot produce code for 4xx it seems.
> > 
> > You should normally not need to build the 4xx bootloader part. Make sure
> > that, i don't know why this happens. Can you look into
> > arch/powerpc/boot/Makefile, to see what option enables the 4xx build,
> > and make sure it is disabled in the main config ?
> 
> That's not true.  All the wrapper bits are built for every board always.

Yes, which is why it fails. But Should they not be conditionally built
upon including support or not for the actual board ? 

I mean, if you have not included 4xx support in the kernel, as is the
case here, it does not make sense to add the 4xx bootwrapper code, no ? 

Friendly,

Sven Luther

  reply	other threads:[~2008-02-05 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 16:29 compile quirk linux-2.6.24 (with workaround) Bernhard Reiter
2008-02-04  9:51 ` Sven Luther
2008-02-04 10:26   ` Bernhard Reiter
2008-02-04 17:34     ` Grant Likely
2008-02-05 13:08   ` Josh Boyer
2008-02-05 14:39     ` Sven Luther [this message]
2008-02-05 15:15       ` Josh Boyer
2008-02-05 15:24         ` Grant Likely
2008-02-05 15:38           ` Josh Boyer
2008-02-05 16:10             ` Olof Johansson
2008-02-06 10:07             ` Bernhard Reiter
2008-02-19  2:52             ` Josh Boyer
2008-02-22 14:50               ` Bernhard Reiter
2008-02-25 11:56                 ` Bernhard Reiter
2008-03-03 17:26                   ` Bernhard Reiter
2008-02-04 21:01 ` Josh Boyer

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=20080205143926.GA9709@powerlinux.fr \
    --to=sven@powerlinux.fr \
    --cc=bernhard@intevation.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).