linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.26 does not boot on Pegasos
Date: Tue, 22 Jul 2008 19:54:57 +0200	[thread overview]
Message-ID: <c331742b5952510a9bce5e654ba293b4@kernel.crashing.org> (raw)
In-Reply-To: <48808914.20702@genesi-usa.com>

>>> If you built this kernel yourself, you need to do it from a system 
>>> with
>>> an up-to-date binutils (2.18) otherwise, it does this.
>
> Note to the linux-ppc guys; is there any changelog entry which reports
> this requirement somewhere? I didn't find one...

That's because there is no such requirement.  2.18 is the latest
version, so it's always wise to test with that in case you have
some problems; but it wouldn't be nice if the kernel can be built
with only one binutils major version.

Please try my build patch for a similar problem, it went into
BenH's tree today.  Would be nice if it was the same problem;
if not, send a proper, _detailed_ bug report here and I'll look
into it.


Segher

  reply	other threads:[~2008-07-22 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 10:00 2.6.26 does not boot on Pegasos Gabriel Paubert
2008-07-15 10:05 ` Benjamin Herrenschmidt
2008-07-15 10:45   ` Gabriel Paubert
2008-07-15 14:17   ` David Woodhouse
2008-07-15 15:27 ` Matt Sealey
2008-07-15 15:59   ` Gabriel Paubert
2008-07-18 12:14     ` Matt Sealey
2008-07-22 17:54       ` Segher Boessenkool [this message]
2008-07-15 16:15   ` Jon Smirl

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=c331742b5952510a9bce5e654ba293b4@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.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).