From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM compile failure in Re: linux-next: Tree for Apr 4
Date: Wed, 4 Apr 2018 10:58:52 -0700 [thread overview]
Message-ID: <20180404175852.GI5700@atomide.com> (raw)
In-Reply-To: <20180404074856.GA9342@amd>
* Pavel Machek <pavel@ucw.cz> [180404 07:50]:
> Hi!
>
> > Please do not add any v4.18 destined stuff to your linux-next included
> > trees until after v4.17-rc1 has been released.
> >
> > Changes since 20180403:
> >
> > The vfs tree still had its build failure for which I reverted a commit.
> >
> > Non-merge commits (relative to Linus' tree): 8505
> > 8493 files changed, 392779 insertions(+), 275941 deletions(-)
> >
> > ----------------------------------------------------------------------------
>
> When trying to build kernel for N900, I get:
>
> CC lib/timerqueue.o
> CC lib/vsprintf.o
> lib/string.c: In function 'strstr':
> lib/string.c:478:8: error: inlining failed in call to
> always_inline 'strlen': function not inlinable
> lib/string.c:903:5: error: called from here
> lib/string.c:478:8: error: inlining failed in call to
> always_inline 'strlen': function not inlinable
> lib/string.c:906:5: error: called from here
> lib/string.c:855:15: error: inlining failed in call to
> always_inline 'memcmp': function not inlinable
> ...
> pavel at duo:/data/l/linux-next-n900$ git branch -l
> * (detached from next-20180403)
>
> I'm using
>
> eval ` eldk-switch.sh -r 5.4 armv7a`
>
> for cross-compilation.
Hmm I'm not seeing build issues with next-20180404, did this somehow
already get sorted out?
Regards,
Tony
next prev parent reply other threads:[~2018-04-04 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180404165559.4cd0c12c@canb.auug.org.au>
2018-04-04 7:48 ` ARM compile failure in Re: linux-next: Tree for Apr 4 Pavel Machek
2018-04-04 17:58 ` Tony Lindgren [this message]
2018-04-04 18:15 ` Pavel Machek
2018-04-04 18:46 ` Pavel Machek
2018-04-04 19:59 ` Tony Lindgren
2018-04-04 20:18 ` FORTIFY_SOURCE breaks ARM compilation in -next -- was " Pavel Machek
2018-04-15 17:39 ` [regression v4.17-rc0] " Pavel Machek
2018-04-15 18:00 ` Kees Cook
2018-04-15 20:58 ` Pavel Machek
2018-04-20 7:34 ` Pavel Machek
2018-04-20 15:05 ` Kees Cook
2018-04-20 17:21 ` Russell King - ARM Linux
2018-04-20 19:15 ` Pavel Machek
2018-04-20 19:18 ` Daniel Micay
2018-04-20 19:28 ` Pavel Machek
2018-04-20 19:30 ` Daniel Micay
2018-04-20 20:30 ` Pavel Machek
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=20180404175852.GI5700@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).