lkml.org 
[lkml]   [2010]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: linux-next: Tree for October 20
From
Hi,

On Mon, Oct 25, 2010 at 4:47 AM, Michal Marek <mmarek@suse.cz> wrote:
> On 21.10.2010 15:09, Christoph Hellwig wrote:
>> I can't even get the required userspace code make oldconfig to compile:
>>
>> hch@brick:~/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.
>
this is at least the third time there is such a report. I did
reproduce this issue while using an external build directory:

From what I remind:

% gmake menuconfig # generate lex.zconf.c
% gmake O=/foo menuconfig # generate lex.zconf.c

% touch scripts/kconfig/lex.zconf.c_shipped

% gmake menuconfig # re-generated lex.zconf.c
% gmake O=/foo menuconfig # did _not_ re-generate lex.zconf.c

However, this tree was dirty (ie. included WIP stuff), switching to a
clean tree, and certainly updating a bunch of timestamps, make it
disappear.

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

\
 
 \ /
  Last update: 2010-10-26 18:25    [W:1.108 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site