lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 26 Sep 2014 10:59:00 +0300
From:	Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	Vineet Gupta <vgupta@...opsys.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux-Next <linux-next@...r.kernel.org>,
	linux <linux@...ts.openrisc.net>, Eric Paris <eparis@...hat.com>
Subject: Re: linux-next: New build failures in Sep 25 tree

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@...ck-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.

Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ