From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org, Alan Modra <amodra@bigpond.net.au>
Subject: Re: linux-next: build failure after merge of the final tree (powerpc related)
Date: Thu, 21 Jun 2012 16:24:56 +1000 [thread overview]
Message-ID: <1340259896.3942.2.camel@pasglop> (raw)
In-Reply-To: <1340256961.1998.11.camel@concordia>
On Thu, 2012-06-21 at 15:36 +1000, Michael Ellerman wrote:
>
> powerpc64-linux-ld: /src/next/net/openvswitch/vport-netdev.c:189:(.text+0x89b990):
> sibling call optimization to `_restgpr0_28' does not allow automatic multiple TOCs;
> recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `_restgpr0_28' extern
>
>
> And those are generated calls so I don't see how we can fix them.
Is this a module ? We should really be linking that stuff directly with the module....
The interesting thing is that we do build everything except a handful of
files with -mminimal-toc unless something's wrong with our main Makefile....
Can you show the full build command that triggers the above ?
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-21 6:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 7:50 linux-next: build failure after merge of the final tree (powerpc related) Stephen Rothwell
2012-06-20 7:50 ` Stephen Rothwell
2012-06-20 10:09 ` Benjamin Herrenschmidt
2012-06-20 10:09 ` Benjamin Herrenschmidt
2012-06-21 5:36 ` Michael Ellerman
2012-06-21 5:36 ` Michael Ellerman
2012-06-21 6:24 ` Benjamin Herrenschmidt [this message]
2012-06-21 7:07 ` Michael Ellerman
2012-06-21 7:07 ` Michael Ellerman
2012-06-21 7:07 ` Michael Ellerman
2012-06-21 7:38 ` Michael Ellerman
2012-06-21 7:38 ` Michael Ellerman
2012-06-21 7:38 ` Michael Ellerman
2012-06-21 10:48 ` Alan Modra
2012-06-21 10:48 ` Alan Modra
2012-06-21 11:43 ` Alan Modra
2012-06-21 11:43 ` Alan Modra
2012-06-22 0:39 ` Michael Ellerman
2012-06-22 0:39 ` Michael Ellerman
2012-06-21 7:29 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 8:49 Stephen Rothwell
2011-12-28 8:49 ` Stephen Rothwell
2011-12-28 8:49 ` Stephen Rothwell
2011-12-28 10:32 ` Benjamin Herrenschmidt
2011-12-28 10:32 ` Benjamin Herrenschmidt
2012-01-02 8:25 ` Grant Likely
2012-01-02 8:25 ` Grant Likely
2012-01-02 8:39 ` Grant Likely
2012-01-02 8:39 ` Grant Likely
2010-09-03 3:24 Stephen Rothwell
2010-09-03 3:24 ` Stephen Rothwell
2010-09-17 4:27 ` Stephen Rothwell
2010-09-17 4:27 ` Stephen Rothwell
2010-07-16 7:19 Stephen Rothwell
2010-07-16 7:19 ` Stephen Rothwell
2010-07-16 7:19 ` Stephen Rothwell
2010-07-19 0:15 ` Benjamin Herrenschmidt
2010-07-19 0:15 ` 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=1340259896.3942.2.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=amodra@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.