From: Guenter Roeck <linux@roeck-us.net>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Fengguang Wu <fengguang.wu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures
Date: Tue, 2 Aug 2016 14:58:39 -0700 [thread overview]
Message-ID: <20160802215839.GA7383@roeck-us.net> (raw)
In-Reply-To: <CAB=NE6U18jv89pxqAeZY8eTj44mq90kyXGaQO-108+ZMTyxQiQ@mail.gmail.com>
On Tue, Aug 02, 2016 at 01:07:09PM -0700, Luis R. Rodriguez wrote:
> Are linux-next builds being tested for powerpc with allyesconfig and
> allmodconfig ? I have some changes I'm making and while debugging my
> build issues I decided to give a clean build a shot and see linux-next
> next-20160729 up to next-20160729 all have build failures without my
> changes. I get:
>
> /opt/gcc-4.9.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
> drivers/built-in.o: .opd is not a regular array of opd entries
> MODPOST vmlinux.o
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> /opt/gcc-4.9.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
> drivers/built-in.o: .opd is not a regular array of opd entries
> drivers/built-in.o: In function `.ipw2100_up':
> ipw2100.c:(.text+0x1ff9c90): relocation truncated to fit:
"relocation truncated to fit" errors are typical for ppc:allyesconfig.
allmodconfig should work, though.
Guenter
next prev parent reply other threads:[~2016-08-02 21:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 20:07 powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures Luis R. Rodriguez
2016-08-02 21:58 ` Guenter Roeck [this message]
2016-08-02 22:02 ` Luis R. Rodriguez
2016-08-02 22:34 ` Arnd Bergmann
2016-08-03 0:23 ` Stephen Rothwell
2016-08-03 7:52 ` Arnd Bergmann
2016-08-03 12:19 ` Stephen Rothwell
2016-08-03 12:29 ` Arnd Bergmann
2016-08-03 15:37 ` Nicholas Piggin
2016-08-03 18:52 ` Arnd Bergmann
2016-08-03 19:44 ` Segher Boessenkool
2016-08-03 20:13 ` Arnd Bergmann
2016-08-11 12:43 ` Nicholas Piggin
2016-08-11 13:04 ` Arnd Bergmann
2016-08-11 13:12 ` Nicholas Piggin
2016-08-11 13:49 ` [TESTING] kbuild: link drivers subdirectories separately Arnd Bergmann
2016-08-11 15:46 ` Arnd Bergmann
2016-08-04 0:10 ` powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures Stephen Rothwell
2016-08-04 9:00 ` Arnd Bergmann
2016-08-04 10:37 ` Arnd Bergmann
2016-08-04 11:47 ` Nicholas Piggin
2016-08-04 12:09 ` Arnd Bergmann
2016-08-04 12:31 ` Nicholas Piggin
2016-08-04 13:54 ` Nicholas Piggin
2016-08-04 15:43 ` Arnd Bergmann
2016-08-04 16:10 ` Arnd Bergmann
2016-08-04 17:06 ` Segher Boessenkool
2016-08-05 8:41 ` Nicholas Piggin
2016-08-05 10:17 ` Arnd Bergmann
2016-08-05 12:26 ` Nicholas Piggin
2016-08-05 16:01 ` Arnd Bergmann
2016-08-05 16:16 ` Nicholas Piggin
2016-08-05 19:16 ` Arnd Bergmann
2016-08-06 4:17 ` Nicholas Piggin
2016-08-06 21:13 ` Arnd Bergmann
2016-08-03 2:46 ` Michael Ellerman
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=20160802215839.GA7383@roeck-us.net \
--to=linux@roeck-us.net \
--cc=benh@kernel.crashing.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@kernel.org \
--cc=mpe@ellerman.id.au \
--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).