On Wed, 2005-03-02 at 16:59 -0600, Roman Zippel wrote:
> In directory ubb:/home/linux-m68k/zippel/linux-native
>
> Log Message:
> import native 2.6.11
>
> C linux/include/linux/sched.h
I tried compiling the tree today, it doesn't seem to work:
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/sched.h:15,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/task_struct.h:127: error: parse error before "cputime_t"
So I added
#include <asm/cputime.h>
to include/linux/task_struct.h. After that it bombs out with the next
error:
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/sched.h:15,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/task_struct.h:149: error: `TASK_COMM_LEN' undeclared here (not in
a function)
So I moved the definition of TASK_COMM_LEN from include/linux/sched.h to
include/linux/task_struct.h.
Then I got the following error:
CC init/do_mounts_initrd.c
In file included from include/asm/unistd.h:414,
from include/linux/unistd.h:9,
from init/do_mounts_initrd.c:2:
include/linux/interrupt.h: In function `sti':
include/linux/interrupt.h:70: error: `current' undeclared (first use in this
function)
include/linux/interrupt.h:70: error: (Each undeclared identifier is reported
only once
include/linux/interrupt.h:70: error: for each function it appears in.)
So I added
#include <asm/current.h>
to include/asm-m68k/thread_info.h.
But that didn't work out so well either:
CC init/do_mounts_initrd.o
In file included from include/asm/unistd.h:415,
from include/linux/unistd.h:9,
from init/do_mounts_initrd.c:2:
include/linux/interrupt.h: In function `sti':
include/linux/interrupt.h:70: error: dereferencing pointer to incomplete type
make[1]: *** [init/do_mounts_initrd.o] Error 1
make: *** [init] Error 2
After that I gave up, because I don't know what includes files I should
change so that include/linux/interrupt.h has access to struct
task_struct and struct thread_struct etc.
Kind regards,
Kars.
-
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
