From: Guenter Roeck <linux@roeck-us.net>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ulf Hansson <ulf.hansson@linaro.org>,
Vineet Gupta <vgupta@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>,
linux <linux@lists.openrisc.net>, Eric Paris <eparis@redhat.com>
Subject: Re: linux-next: New build failures in Sep 25 tree
Date: Fri, 26 Sep 2014 06:32:33 -0700 [thread overview]
Message-ID: <54256AF1.6030800@roeck-us.net> (raw)
In-Reply-To: <20140926075859.GA21697@chokladfabriken.org>
On 09/26/2014 12:59 AM, Stefan Kristiansson wrote:
> On Fri, Sep 26, 2014 at 08:30:57AM +0200, Geert Uytterhoeven wrote:
>> Hi Günther,
>>
>> [cc openrisc]
>>
>> On Thu, Sep 25, 2014 at 10:25 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>>> New build failures:
>>
>>> openrisc-defconfig
>>>
>>> In file included from arch/openrisc/kernel/signal.c:31:0:
>>> ./arch/openrisc/include/asm/syscall.h: In function 'syscall_get_arch':
>>> ./arch/openrisc/include/asm/syscall.h:77:9: error: 'EM_OPENRISC' undeclared
>>
>> That's not a new one. It's been failing for half or year or so.
>>
>> If you only see it now, that means something else got fixed ;-)
>>
>
>>From what I can see, it's caused by
> ce5d112827e5 ("ARCH: AUDIT: implement syscall_get_arch for all arches")
> that got (re?)introduced two days ago.
>
> To me it seems that the problem is that EM_OPENRISC is
> missing in include/uapi/linux/elf-em.h, but if that's the case,
> I think microblaze have the same problem with that patch applied.
>
Microblaze builds for some reason. But, yes, that commit is from March.
Maybe that is where I remember it from.
You are right, it builds if I add the define. I'll submit a patch to fix
the problem if the resulting image builds.
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ulf Hansson <ulf.hansson@linaro.org>,
Vineet Gupta <vgupta@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>,
linux <linux@openrisc.net>, Eric Paris <eparis@redhat.com>
Subject: Re: linux-next: New build failures in Sep 25 tree
Date: Fri, 26 Sep 2014 06:32:33 -0700 [thread overview]
Message-ID: <54256AF1.6030800@roeck-us.net> (raw)
In-Reply-To: <20140926075859.GA21697@chokladfabriken.org>
On 09/26/2014 12:59 AM, Stefan Kristiansson wrote:
> On Fri, Sep 26, 2014 at 08:30:57AM +0200, Geert Uytterhoeven wrote:
>> Hi Günther,
>>
>> [cc openrisc]
>>
>> On Thu, Sep 25, 2014 at 10:25 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>>> New build failures:
>>
>>> openrisc-defconfig
>>>
>>> In file included from arch/openrisc/kernel/signal.c:31:0:
>>> ./arch/openrisc/include/asm/syscall.h: In function 'syscall_get_arch':
>>> ./arch/openrisc/include/asm/syscall.h:77:9: error: 'EM_OPENRISC' undeclared
>>
>> That's not a new one. It's been failing for half or year or so.
>>
>> If you only see it now, that means something else got fixed ;-)
>>
>
>>From what I can see, it's caused by
> ce5d112827e5 ("ARCH: AUDIT: implement syscall_get_arch for all arches")
> that got (re?)introduced two days ago.
>
> To me it seems that the problem is that EM_OPENRISC is
> missing in include/uapi/linux/elf-em.h, but if that's the case,
> I think microblaze have the same problem with that patch applied.
>
Microblaze builds for some reason. But, yes, that commit is from March.
Maybe that is where I remember it from.
You are right, it builds if I add the define. I'll submit a patch to fix
the problem if the resulting image builds.
Guenter
next prev parent reply other threads:[~2014-09-26 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 20:25 linux-next: New build failures in Sep 25 tree Guenter Roeck
2014-09-26 2:23 ` Vineet Gupta
2014-09-26 6:30 ` Geert Uytterhoeven
2014-09-26 6:30 ` Geert Uytterhoeven
2014-09-26 6:46 ` Guenter Roeck
2014-09-26 6:46 ` Guenter Roeck
2014-09-26 7:59 ` Stefan Kristiansson
2014-09-26 7:59 ` Stefan Kristiansson
2014-09-26 13:32 ` Guenter Roeck [this message]
2014-09-26 13:32 ` Guenter Roeck
2014-09-26 15:08 ` Eric Paris
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=54256AF1.6030800@roeck-us.net \
--to=linux@roeck-us.net \
--cc=eparis@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@lists.openrisc.net \
--cc=sfr@canb.auug.org.au \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=ulf.hansson@linaro.org \
--cc=vgupta@synopsys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.