From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
Alan Modra <amodra@bigpond.net.au>,
Milton Miller <miltonm@bga.com>
Subject: Re: [HOW] binutils-2.17 breaks the 2.6.26 kernel
Date: Thu, 17 Jul 2008 15:53:07 +0200 [thread overview]
Message-ID: <3400bffa9d49e09b00e04cafcd751322@kernel.crashing.org> (raw)
In-Reply-To: <9e4733910807161738g58da8bd7v78e9d50dc4d846cb@mail.gmail.com>
> Previous threads have mentioned that binutil-2.17 is broken for
> building powerpc kernels. It is fixed in binutils-2.18.
Yes.
> I have encountered this and upgrading to 2.18 fixed my build. The
> symptom is large kernel sizes and a long time in gzip. In my case it
> was gziping a 2GB file.
Are you using a "binary" (non-ELF) image file? This sounds like a
different problem, caused by the kernel linker script not handling
the build-id section correctly -- it places it at 0, and the rest
of the kernel at 3GB, you can imagine the rest. I've seen this
on various embedded targets, but not on PowerPC iirc -- maybe I
don't build any affected defconfig, what's yours?
I have a working (tested! thanks Milton) workaround for the current
problem, will send it later today. This problem funnily is hidden
by the presence of build-id :-)
Segher
next prev parent reply other threads:[~2008-07-17 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 16:21 [HOW] binutils-2.17 breaks the 2.6.26 kernel Milton Miller
2008-07-16 23:41 ` Segher Boessenkool
2008-07-17 0:38 ` Jon Smirl
2008-07-17 0:49 ` Gabriel Paubert
2008-07-17 13:53 ` Segher Boessenkool [this message]
2008-07-21 16:49 ` Rune Torgersen
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=3400bffa9d49e09b00e04cafcd751322@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@bigpond.net.au \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.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).