Re: UML defconfig building failed again

[Sam Ravnborg]

On Tue, Nov 06, 2007 at 02:11:43PM +0000, Al Viro wrote:
> On Tue, Nov 06, 2007 at 07:46:02PM +0800, WANG Cong wrote:
> > 
> > Hi, Jeff!
> > 
> > I used today's linus-tree and defconfig to compile uml, but it failed. Error messages are
> > things like:
> > 
> > In file included from include/asm/processor-generic.h:13,
> >                  from include/asm/processor.h:77,
> >                  from include/asm/thread_info.h:11,
> >                  from include/linux/thread_info.h:21,
> >                  from include/linux/preempt.h:9,
> >                  from include/linux/spinlock.h:49,
> >                  from include/linux/seqlock.h:29,
> >                  from include/linux/time.h:8,
> >                  from include/linux/timex.h:57,
> >                  from include/linux/sched.h:53,
> >                  from arch/um/include/sysdep/kernel-offsets.h:2,
> >                  from arch/um/kernel/asm-offsets.c:1:
> > include/asm/ptrace.h:50: warning: ???struct user_fxsr_struct??? declared inside parameter list
> > include/asm/ptrace.h:50: warning: its scope is only this definition or declaration, which is probably not what you want
> > include/asm/ptrace.h:52: warning: ???struct user_fxsr_struct??? declared inside parameter list
> > In file included from include/linux/timer.h:5,
> >                  from include/linux/sched.h:87,
> >                  from arch/um/include/sysdep/kernel-offsets.h:2,
> >                  from arch/um/kernel/asm-offsets.c:1:
> > include/linux/ktime.h: In function ???ktime_set???:
> > include/linux/ktime.h:84: warning: comparison is always false due to limited range of data type
> > 
> > {snip}
> > 
> > It seems like CONFIG_X86_32 was not set. Any ideas?
> 
> Sigh...  Kbuild breakage this time...  See if %s/\<[AC]FLAGS\>/KBUILD_&/g
> in arch/um/Makefile-i386 helps.
Ups - my bad.
I have somehow overlooked those two assignments in the middle.

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