From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Helge Deller <deller@gmx.de>,
James.Bottomley@hansenpartnership.com,
linux-parisc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] parisc: signal: remove _SA_SIGGFAULT
Date: Tue, 15 Dec 2020 19:54:32 +0530 [thread overview]
Message-ID: <CA+G9fYtgKFUsiY2x8Ue-cnO2Jr1+teQZ_3TbKC+eD9c6OpkPGg@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYtNgeOgymsVwj423eXOFP1B=mS4KKvy+1Bu3tUapXyxDA@mail.gmail.com>
Anders,
On Wed, 2 Dec 2020 at 13:31, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Anders,
>
> On Fri, 27 Nov 2020 at 04:10, Anders Roxell <anders.roxell@linaro.org> wrote:
> >
> > On Thu, 26 Nov 2020 at 15:46, Helge Deller <deller@gmx.de> wrote:
> > >
> > > On 11/26/20 2:06 PM, Anders Roxell wrote:
> > > > When building tinyconfig on parisc the following error shows up:
> > > >
> > > > /tmp/kernel/signal.c: In function 'do_sigaction':
> > > > /tmp/arch/parisc/include/asm/signal.h:24:30: error: '_SA_SIGGFAULT' undeclared (first use in this function); did you mean 'SIL_FAULT'?
> > > > #define __ARCH_UAPI_SA_FLAGS _SA_SIGGFAULT
> > > > ^~~~~~~~~~~~~
I see these build failures on Linux mainline.
ref:
https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline/-/jobs/911416687
Steps to reproduce:
-----------------------------
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds across a variety of
# architectures, toolchains, kernel configurations, and make targets.
#
# TuxMake supports the concept of runtimes.
# See https://docs.tuxmake.org/runtimes/, for that to work it requires
# that you install podman or docker on your system.
#
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
tuxmake --runtime docker --target-arch parisc --toolchain gcc-9
--kconfig defconfig
- Naresh
prev parent reply other threads:[~2020-12-15 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:06 Anders Roxell
2020-11-26 14:46 ` Helge Deller
2020-11-26 22:39 ` Anders Roxell
2020-12-02 8:01 ` Naresh Kamboju
2020-12-15 14:24 ` Naresh Kamboju [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=CA+G9fYtgKFUsiY2x8Ue-cnO2Jr1+teQZ_3TbKC+eD9c6OpkPGg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=anders.roxell@linaro.org \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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
all inboxes | Powered by JetHome®