All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: segher@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: gcc-4.2.0 breakage on powerpc?
Date: Sat, 19 May 2007 17:23:38 +0200	[thread overview]
Message-ID: <464F167A.1090706@anagramm.de> (raw)
In-Reply-To: <200705190953.l4J9rjO2024613@harpo.it.uu.se>

Mikael Pettersson schrieb:
> On Sat, 19 May 2007 01:39:43 +0200, Segher Boessenkool wrote:
>>> and we'll end up
>>> having major kernel releases which don't build on i386 with major gcc
>>> releases, which isn't altogether desirable.
>> Yeah, like 4.2.0 with powerpc.  Seems like no one tested it :-(
> 
> Details please. What exactly are the gcc-4.2.0 problems on powerpc?

[embedded platform!]
Over here, the 2.6.21.1 Kernel _builds_ fine with gcc-4.2.0 on an mpc8540 e500 powerpc
(mpc8540_ads_defconfig) but it just crashes silently on boot. But that's IMHO a
DeviceTree/U-Boot issue I haven't solved yet.

$ uname -a
Linux ecam.anagramm.de 2.6.21-rc5-g9a5ee4cc #4 Mon Apr 2 21:31:53 CEST 2007 ppc e500 GNU/Linux
ARCH=ppc compiled with GCC-4.1.2 works fine.

Greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm-technology.com
Phone: +49-89-741518-50
Fax: +49-89-741518-19

  parent reply	other threads:[~2007-05-19 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  9:53 gcc-4.2.0 breakage on powerpc? Mikael Pettersson
2007-05-19 12:51 ` Segher Boessenkool
2007-05-19 16:11   ` Segher Boessenkool
2007-05-19 16:11     ` Segher Boessenkool
2007-05-19 15:23 ` Clemens Koller [this message]
2007-05-19 16:13   ` Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2007-05-19 17:28 Mikael Pettersson
2007-05-19 17:28 ` Mikael Pettersson

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=464F167A.1090706@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=segher@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.