From: Alan Modra <amodra@bigpond.net.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: linux-next: build failure
Date: Wed, 8 Apr 2009 14:42:03 +0930 [thread overview]
Message-ID: <20090408051202.GA27796@bubble.grove.modra.org> (raw)
In-Reply-To: <20090408140407.14dc5242.sfr@canb.auug.org.au>
On Wed, Apr 08, 2009 at 02:04:07PM +1000, Stephen Rothwell wrote:
> LD vmlinux.o
> powerpc-linux-ld: TOC section size exceeds 64k
I'm starting to sound like a cracked record, but I'll say it again:
ld -r does not merely package together object files, it transforms
them. Try using thin archives instead.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2009-04-08 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 4:04 linux-next: build failure Stephen Rothwell
2009-04-08 5:12 ` Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-16 9:29 Stephen Rothwell
2008-10-16 10:39 ` Ingo Molnar
2008-10-16 16:11 ` Jeremy Fitzhardinge
2008-10-16 16:14 ` Ingo Molnar
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=20090408051202.GA27796@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).