linux-kernel - Re: linux-next: Tree for October 20

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:	Mon, 25 Oct 2010 10:47:51 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for October 20

On 21.10.2010 15:09, Christoph Hellwig wrote:
> I can't even get the required userspace code make oldconfig to compile:
> 
> hch@...ck:~/work/linux-2.6/obj-kvm$ make oldconfig
> make -C /home/hch/work/linux-2.6 O=/home/hch/work/linux-2.6/obj-kvm/. oldconfig
>   GEN     /home/hch/work/linux-2.6/obj-kvm/Makefile
>   HOSTCC  scripts/kconfig/zconf.tab.o
> In file included from scripts/kconfig/zconf.tab.c:2481:
> scripts/kconfig/lex.zconf.c:2425: error: conflicting types for 'zconf_curname'
> /home/hch/work/linux-2.6/scripts/kconfig/lkc.h:79: note: previous declaration of 'zconf_curname' was here
> scripts/kconfig/lex.zconf.c: In function 'zconf_curname':
> scripts/kconfig/lex.zconf.c:2427: warning: return discards qualifiers from pointer target type

The zconf_curname() prototype was changed in 2e7a091 and the
scripts/kconfig/lex.zconf.c_shipped file was updated as well. What
probably happened is that you ended up using an updated
scripts/kconfig/lkc.h header versus an old version of
scripts/kconfig/lex.zconf.c. Ie. the rule that copies
scripts/kconfig/lex.zconf.c_shipped to scripts/kconfig/lex.zconf.c did
not trigger, very strange. I'll look further.

Michal
--
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/