From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, Thomas Gleixner <tglx@linutronix.de>,
linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: powerpc build failure
Date: Wed, 11 Jun 2008 11:59:51 +0200 [thread overview]
Message-ID: <20080611095951.GB14033@elte.hu> (raw)
In-Reply-To: <20080611192748.686236fd.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> vmlinux.o: In function `ipx_ioctl':
> /scratch/sfr/next/net/ipx/af_ipx.c:1830: relocation truncated to fit: R_PPC64_REL24 against symbol `._mcount' defined in .text section in vmlinux.o
>
> (and lots more similar)
>
> I am assuming that this has something to do with how big vmlinux is
> for allyesconfig and the addition of -pg to KBUILD_CFLAGS for ftrace.
could this be a tool chain limitation perhaps, or a gcc bug? Or does the
allyesconfig size go beyond some fundamental hardware limitation. (i
doubt it's the latter)
Ingo
next prev parent reply other threads:[~2008-06-11 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:27 linux-next: powerpc build failure Stephen Rothwell
2008-06-11 9:59 ` Ingo Molnar [this message]
2008-06-12 1:38 ` Paul Mackerras
2008-06-12 5:33 ` Alan Modra
2008-06-12 7:05 ` Stephen Rothwell
2008-06-12 7:16 ` Ingo Molnar
2008-06-12 7:27 ` Stephen Rothwell
2008-06-12 7:47 ` Ingo Molnar
2008-06-12 7:23 ` Benjamin Herrenschmidt
2008-06-12 7:24 ` Stephen Rothwell
2008-06-12 18:12 ` Sam Ravnborg
2008-06-12 8:15 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 6:54 Stephen Rothwell
2008-06-10 7:20 ` Benjamin Herrenschmidt
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=20080611095951.GB14033@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).