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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Sep 2014 06:24:44 -0700
From:	Guenter Roeck <>
To:	Geert Uytterhoeven <>
CC:	Jesper Nilsson <>,
	"" <>,
	Cris <>,
	Jesper Nilsson <>,
	Mikael Starvik <>,
	Grant Likely <>,
	"Edgar E. Iglesias" <>
Subject: Re: Status of 'cris' architecture support in Linux kernel

On 09/16/2014 12:23 AM, Geert Uytterhoeven wrote:
> Hi G√ľnther,
> On Mon, Sep 15, 2014 at 9:55 PM, Guenter Roeck <> wrote:
>>>> ./scripts/Makefile.headersinst:14: arch/cris/include/uapi/asm/arch-v10/Kbuild:
>>>>      No such file or directory
>>>> make[2]: *** No rule to make target `arch/cris/include/uapi/asm/arch-v10/Kbuild'.  Stop.
>>> Yes, known error, I believe that Sam Ravnborg's patch will correct this.
>> Is that patch available in public ? Sam's response seems to suggest that he
>> sent it to Michael (Mikael ?) who wanted to handle it, but I don't find a
>> matching patch in public archives.
Must be blind. Looked at the series for a long time but didn't see it.

>>> On a tangential note, my automatic (minimal) builds does not do
>>> make install, so I haven't seen this error. :-P
>> Mine not either ;-). I only found it because I tried to build an initramfs
>> which needs installed headers.
> We need an Auto-Builder Consolidation Project ;-)

More likely we need someone to actually look at build results. Like all the -next
builds that are currently failing, and I bet those responsible are not even aware
of it. Any ideas ?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists