Re: [uml-devel] uml compile error

2008-02-13 Thread Rafael J. Wysocki
On Friday, 8 of February 2008, Adrian Bunk wrote: > Commit dd2cc4dff3b08ab54c4c177a080046bcc84ac41d broke uml: > > <-- snip --> > > ... > CC fs/hostfs/hostfs_kern.o > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/hostfs/hostfs_kern.c: In > function ‘hostfs_show_options’: > /home/bunk/linu

Re: [uml-devel] uml compile error

2008-02-13 Thread Adrian Bunk
On Wed, Feb 13, 2008 at 11:24:31PM +0100, Rafael J. Wysocki wrote: > On Friday, 8 of February 2008, Adrian Bunk wrote: > > Commit dd2cc4dff3b08ab54c4c177a080046bcc84ac41d broke uml: > > > > <-- snip --> > > > > ... > > CC fs/hostfs/hostfs_kern.o > > /home/bunk/linux/kernel-2.6/git/linux-2

Re: [uml-devel] uml compile error

2008-02-08 Thread Jiri Kosina
On Sat, 9 Feb 2008, Adrian Bunk wrote: > Commit dd2cc4dff3b08ab54c4c177a080046bcc84ac41d broke uml: > <-- snip --> > ... > CC fs/hostfs/hostfs_kern.o > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/hostfs/hostfs_kern.c: In > function 'hostfs_show_options': > /home/bunk/linux/kernel-2.6/git

Re: [uml-devel] uml compile error

2008-02-08 Thread Adrian Bunk
On Sat, Feb 09, 2008 at 01:05:15AM +0100, Jiri Kosina wrote: > On Sat, 9 Feb 2008, Adrian Bunk wrote: > > > Commit dd2cc4dff3b08ab54c4c177a080046bcc84ac41d broke uml: > > <-- snip --> > > ... > > CC fs/hostfs/hostfs_kern.o > > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/hostfs/hostfs_kern

[uml-devel] uml compile error

2008-02-08 Thread Adrian Bunk
Commit dd2cc4dff3b08ab54c4c177a080046bcc84ac41d broke uml: <-- snip --> ... CC fs/hostfs/hostfs_kern.o /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/hostfs/hostfs_kern.c: In function ‘hostfs_show_options’: /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/hostfs/hostfs_kern.c:328: error: dere

[uml-devel] [UML] Compile error when building with seperate source and object directories

2005-04-26 Thread Ryan Anderson
I've been seeing a build error when trying to build User Mode Linux on an x86-32 host (Athlon, fwiw). The kernel I'm building is a 1-day old pull from git. This error is not new, though. I thought it was merely an artifact of a patch stuck in a queue at first so I didn't mention it right away.