From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures
Date: Wed, 03 Aug 2016 09:52:23 +0200 [thread overview]
Message-ID: <1944325.MtNrGQyQle@wuerfel> (raw)
In-Reply-To: <20160803102324.6372e66a@canb.auug.org.au>
On Wednesday, August 3, 2016 10:23:24 AM CEST Stephen Rothwell wrote:
> Hi Luis,
>
> On Wed, 3 Aug 2016 00:02:43 +0200 "Luis R. Rodriguez" <mcgrof@kernel.org> wrote:
> >
> > Thanks for the confirmation. For how long is it known this is broken?
> > Does anyone care and fix these ? Or is this best effort?
>
> This has been broken for many years
>
> I have a couple of times almost fixed it, but it requires that we
> change from using "ld -r" to build the built-in.o objects and some
> changes to the powerpc head.S code ... I will give it another shot now
> that the merge window is almost over (and linux-next goes into its
> quieter time).
Using a different way to link the kernel would also help us with
the remaining allyesconfig problem on ARM, as the problem is only in
'ld -r' not producing trampolines for symbols that later cannot get
them any more. It would probably also help building with ld.gold,
which is currently not working.
What is your suggested alternative?
Arnd
next prev parent reply other threads:[~2016-08-03 7:54 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
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 [this message]
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=1944325.MtNrGQyQle@wuerfel \
--to=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@kernel.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).