linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linuxppc-dev@ozlabs.org, robert.karl.berger@gmail.com
Subject: Re: kilauea compilation breaks with v3.3 kernel and ELDK 4.2
Date: Wed, 21 Mar 2012 17:25:49 +0100	[thread overview]
Message-ID: <20120321162549.8C1D0202A4D@gemini.denx.de> (raw)
In-Reply-To: <CA+5PVA7+vPZmLBzkXOFwTM+kLMYHPDgVW4Jcm91XSxW=Ng-Y6g@mail.gmail.com>

Dear Josh,

In message <CA+5PVA7+vPZmLBzkXOFwTM+kLMYHPDgVW4Jcm91XSxW=Ng-Y6g@mail.gmail.com> you wrote:
>
> > 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.
> 
> Sigh.  GCC 4.2 is pretty old at this point.

But still rock-solid ...  We use it a lot, especially as reference for
more recent (and sometimes more broken) versions of GCC.

> All of the stuff in arch/powerpc/boot/ is built regardless of the
> configured board and stuffed into a wrapper.a archive.  Then the
> individual board targets are built and the necessary pieces are pulled
> from the wrapper.a file.

This appears to be a pretty inefficient approach.  Why don't we build
only the files we actually need?  That would save a bit of build time.

> > Please advise.
> 
> If upgrading ELDK is an option for you, it will get you the quickest
> solution.  Otherwise we'll need to figure out how to stub out the
> instruction in boot/dcr.h and use the asm long trick.  Ew.  I can look
> at that next week.

Thanks a lot in advance!

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It is wrong always, everywhere and for everyone to  believe  anything
upon  insufficient  evidence.  - W. K. Clifford, British philosopher,
circa 1876

  reply	other threads:[~2012-03-21 16:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 12:10 kilauea compilation breaks with v3.3 kernel and ELDK 4.2 Robert Berger
2012-03-21 13:29 ` Josh Boyer
2012-03-21 16:25   ` Wolfgang Denk [this message]
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=20120321162549.8C1D0202A4D@gemini.denx.de \
    --to=wd@denx.de \
    --cc=jwboyer@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=robert.karl.berger@gmail.com \
    /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).