public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Robert Berger <robert.karl.berger@gmail•com>
To: linuxppc-dev@ozlabs•org
Subject: kilauea compilation breaks with v3.3 kernel and ELDK 4.2
Date: Wed, 21 Mar 2012 14:10:59 +0200	[thread overview]
Message-ID: <4F69C553.6070409@gmail.com> (raw)

Hi,

Up to 3.2.x I was able to compile a mainline kernel for the kilauea
board, but...

http://git.denx.de/?p=linux-denx.git;a=commitdiff;h=075bcf5879225d0c2a119c23d8046b890e051e81

shows, that mfdcrx was introduced in the v3.3 kernel.

The problem is that for ppc-linux-gcc (GCC) 4.2.2 (which comes with the
ELDK 4.2) this assembly instruction is not known and the build breaks.

There are some obvious workarounds, like using a more recent toolchain
(e.g ELDK 5.x) or use make -k to keep on compiling even when there is an
error as much as possible;)

What puzzles me is that also stuff for boards is being compiled which is
not really needed like treeboot-currituck.c even when I configure the
kernel for a kilauea board.

Is this on purpose and if so why?

Please advise.

Regards,

Robert
..."But I have a slowly coagulating theory that the size of a project is
directly proportional to the possibility that significant bugs will crop
up. Exponentiate for each additional programmer involved." - Steven K.
Halliburton

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

             reply	other threads:[~2012-03-21 12:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 12:10 Robert Berger [this message]
2012-03-21 13:29 ` kilauea compilation breaks with v3.3 kernel and ELDK 4.2 Josh Boyer
2012-03-21 16:25   ` Wolfgang Denk
2012-03-24 23:53     ` Benjamin Herrenschmidt
2012-03-26 13:36       ` Josh Boyer
2012-03-30 22:53         ` Frank Svendsbøe
2012-03-31  0:03           ` Benjamin Herrenschmidt
2012-04-01 22:14             ` Frank E. Svendsbøe
2012-04-02  2:01               ` Benjamin Herrenschmidt
2012-04-02  6:28                 ` Tony Breeds
2012-04-02  8:37                   ` Frank E. Svendsbøe
2012-05-06 14:37                   ` Robert Berger
2012-05-17 14:37                     ` Frank Svendsbøe
2012-04-02 12:10             ` Josh Boyer
2012-04-02 21:08               ` Benjamin Herrenschmidt
2012-04-02 21:26                 ` Josh Boyer
2012-04-04 19:21               ` Wolfgang Denk
2012-04-05  0:02                 ` Stephen Rothwell
2012-04-05 17:44                   ` Wolfgang Denk
2012-03-21 22:14 ` Tony Breeds
2012-03-21 22:34   ` Wolfgang Denk

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=4F69C553.6070409@gmail.com \
    --to=robert.karl.berger@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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