From: Michael Ellerman <mpe@ellerman.id.au>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: syscall statx not implemented on powerpc
Date: Wed, 15 Mar 2017 11:08:38 +1100 [thread overview]
Message-ID: <87fuifv1tl.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <67f921484d2e42a8975361e821a4b2a7@svr-chch-ex1.atlnz.lc>
Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
> On 15/03/17 00:57, Michael Ellerman wrote:
>> Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
>>> On 13/03/17 21:52, Chandan Rajendra wrote:
>>>> On Monday, March 13, 2017 03:33:07 AM Chris Packham wrote:
>>>>> I've just attempted to build a powerpc kernel from 4.11-rc2 using a
>>>>> custom defconfig (available on request) and I'm hitting the following
>>>>> error in the early stages of compilation.
>>>>>
>>>>> <stdin>:1325:2: error: #warning syscall statx not implemented [-Werror=cpp]
>>>>>
>>>>> Same thing seems to happen with mpc85xx_basic_defconfig.
>>>>>
>>>>> I don't actually need this syscall so I'd be happy to turn something off
>>>>> to get things building. I did a quick search and couldn't see anything
>>>>> on linuxppc-dev but google keeps correcting "statx" to "stats" so I
>>>>> could have missed it.
>>>>
>>>> The upstream commit
>>>> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a528d35e8bfcc521d7cb70aaf03e1bd296c8493f)
>>>> that introduces the statx syscall provides a test program. I will wire-up the
>>>> syscall on ppc64, run that test program and post the patch if the test program
>>>> works well.
>>>
>>> Thanks, I'd be happy to test a patch here.
>>>
>>> In the meantime I worked around the build issue by adding __INGORE_statx
>>> to checksyscalls.sh.
>>
>> Is it actually breaking the build? It's meant to be a warning, and
>> that's all I get.
>
> It breaks my builds for ppc and arm. We do have KCFLAGS=-Werror in our
> environment but KCPPFLAGS= is not set so I'm not sure why it's stopping
> compilation.
OK, I guess that must be it.
We turn on -Werror for all of arch/powerpc by default (unless
CONFIG_PPC_DISABLE_WERROR=y), but the syscall checking script is not
under arch/powerpc so shouldn't be affected by that.
cheers
prev parent reply other threads:[~2017-03-15 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 3:33 syscall statx not implemented on powerpc Chris Packham
2017-03-13 8:51 ` Chandan Rajendra
2017-03-13 20:01 ` Chris Packham
2017-03-14 11:57 ` Michael Ellerman
2017-03-14 19:31 ` Chris Packham
2017-03-15 0:08 ` Michael Ellerman [this message]
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=87fuifv1tl.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=chandan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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