chud wrote:
> I built and booted the 2.6 kernel on RH9 a few weeks ago. I ran
> make oldconfig first, rather than make xconfig as you did. This
> gave me a bootable kernel. At that point you have a workable
> config that you can tweak.

After I ran make oldconfig, ran make and again it failed. The following is
the output:
------------------------------
[root@localhost linux-2.6.0-test1]# make
CC scripts/empty.o
MKELF scripts/elfconfig.h
HOSTCC scripts/file2alias.o
HOSTCC scripts/modpost.o
HOSTLD scripts/modpost
SPLIT include/linux/autoconf.h -> include/config/*
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
CC [M] drivers/char/riscom8.o
In file included from drivers/char/riscom8.c:51:
drivers/char/riscom8.h:84: field `tqueue' has incomplete type
drivers/char/riscom8.h:85: field `tqueue_hangup' has incomplete type
drivers/char/riscom8.c:84: warning: type defaults to `int' in declaration of
`DECLARE_TASK_QUEUE'
drivers/char/riscom8.c:84: warning: parameter names (without types) in
function declaration
drivers/char/riscom8.c:135: confused by earlier errors, bailing out
make[2]: *** [drivers/char/riscom8.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
----------------------------------

Any more repair work that can be attempted?

Srikanth

On Sat, 16 Aug 2003 08:13:52 +0530, SRIKANTH NS wrote:

> In file included from drivers/char/riscom8.c:51:
> drivers/char/riscom8.h:84: field `tqueue' has incomplete type
> drivers/char/riscom8.h:85: field `tqueue_hangup' has incomplete type
> drivers/char/riscom8.c:84: warning: type defaults to `int' in declaration of
> `DECLARE_TASK_QUEUE'
> drivers/char/riscom8.c:84: warning: parameter names (without types) in
> function declaration
> drivers/char/riscom8.c:135: confused by earlier errors, bailing out
> make[2]: *** [drivers/char/riscom8.o] Error 1
> make[1]: *** [drivers/char] Error 2
> make: *** [drivers] Error 2
> ----------------------------------

Looks like the compiler doesn't like what it's seeing in some
header file(s). Maybe your kernel headers don't match the version
of the kernel you are building, or your include path is wrong, or
both. My guess is there's something wrong in your build environment.
You shouldn't be having any problem building the 2.6.0-test1 kernel
on RedHat.