linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Reiter <bernhard@intevation.de>
To: debian-powerpc@lists.debian.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: compile quirk linux-2.6.24 (with workaround)
Date: Mon, 25 Feb 2008 12:56:35 +0100	[thread overview]
Message-ID: <200802251256.41037.bernhard@intevation.de> (raw)
In-Reply-To: <200802221550.27093.bernhard@intevation.de>

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

On Friday 22 February 2008 15:50, Bernhard Reiter wrote:
> > Ok, so it seems -mcpu=440 was added in gcc 3.4.  The -mcpu=405 option
> > has been around since 2001.  Seeing as how there really isn't anything
> > 440 specific in the files effected, we should be able to pass -mcpu=405
> > for everything and have it still work.
> >
> > Bernhard, can you try the patch below?
>
> I will test it in the next days.

Done. Looks good.
(I did _not_ do a full rebuild and installation, only a build test.
I will do a full blown test with 2.6.24.3.)

> The short test for my sarge compiler makes me optimistic:
>
> dpkg -l gcc | grep gcc
> ii  gcc            3.3.5-3        The GNU C compiler
> bernhard@burn:~/tmp$ gcc -mcpu=440 x.c
> cc1: error: bad value (440) for -mcpu= switch
> bernhard@burn:~/tmp$ gcc -mcpu=405 x.c
> bernhard@burn:~/tmp$
>
> > -$(obj)/cuboot-katmai.o: BOOTCFLAGS += -mcpu=440
> > +$(obj)/4xx.o: BOOTCFLAGS += -mcpu=405

Note: Your original did not fully apply, I think it had lines like
-$(obj)/cuboot-taishan.o: BOOTCFLAGS += -mcpu=440
-$(obj)/cuboot-katmai.o: BOOTCFLAGS += -mcpu=440
which I did not have in my 2.6.24.
Probably because you've used a git version of linux.
What I did was to change the similiar occurances from 440 to 405.

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-25 11:56 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
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 [this message]
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=200802251256.41037.bernhard@intevation.de \
    --to=bernhard@intevation.de \
    --cc=debian-powerpc@lists.debian.org \
    --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).