RE: actual errors from demo-sh3.sh build

["Dave Korn" <dave dot korn at artimi dot com>]

----Original Message----
>From: Robert P. J. Day
>Sent: 06 September 2005 15:28

> On Tue, 6 Sep 2005, Dave Korn wrote:
> 
>> ----Original Message----
>>> From: Robert P. J. Day
>>> Sent: 06 September 2005 14:47

>>>   HOSTCC  scripts/kconfig/mconf.o
>>> scripts/kconfig/mconf.c:91: error: static declaration of
>>> â??current_menuâ?? follows non-static declaration
>>> scripts/kconfig/lkc.h:63: error: previous declaration of
>>> â??current_menuâ?? was here make[1]: *** [scripts/kconfig/mconf.o]
>>> Error 1 
>>> make: *** [oldconfig] Error 2

>>   OK, this is a real bug in the source, and the new compiler has stricter
>> error detection, so it's started to trip it...
> 
> it occurs to me only now (since it's been a while since i've played
> with this) that this is a kernel config error but, if i have no need
> to build the kernel, all i need is the sanitized headers.

  I'm not sure I get your meaning by 'kernel config error': it's an error in
the parts of the kernel code that generate the config, yes, but it's not an
error in the actual set of config options you've selected: those lines are
like that in the original source tarball and it is unambigouously a
programming error by the kernel team.
 
> so can't i just blow by this by removing LINUX_DIR and using the
> sanitized headers?  and removing KERNELCONFIG as well, i would think.

  Well, I don't know; I don't have a lot of experience with tricky kludges
in the kernel build process.  My suggestion would just be to fix the bug:
rename that current_menu var in mconf.c or just make it non-static.

  BTW we're not the only people to discuss this:

http://www.google.co.uk/search?q=error%3A+static+declaration+of+current_menu
+follows+non-static+declaration&sourceid=mozilla-search&start=0&start=0&ie=u
tf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-GB:official


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com