Very Computer

Hi all,

I reallt need to recompile my kernel because I want to integrate the ip_masq_h323.c into my box. So, I am
running RH 7.2, which is kernel 2.4, but h323 only supports kernel 2.2.x, so I get the latest 2.2.x kernel
from rpmfind.net, (kernel-source-2.2.19-7.08) as well as kernel-header from 7.0 CD (since 7.0 is running
kernel 2.2.19).

So come to the standard stff, from make mrproper to make bzImage. No problem ! The problem is coming from
make modules, not the addin module but ftape (I am not going to use it anyway). I don't know what is the
reason behind, but it gave me a bunch of crappy messages and end the compilation process in  ERROR. Is there
somebody having the same problem and can give me some help ? This is so annoying. Thanks !!

Let me provide the log to give yuo some idea....

ftape_syms.c:56:1: warning: pasting "(" and "ftape_get_bad_sector_entry"
does not give a valid preprocessing token
ftape_syms.c:57:1: warning: pasting "(" and "ftape_find_end_of_bsm_list"
does not give a valid preprocessing token
ftape_syms.c:59:1: warning: pasting "(" and "ftape_set_state" does not give
a valid preprocessing token
ftape_syms.c:61:1: warning: pasting "(" and "ftape_seek_to_bot" does not
give a valid preprocessing token
ftape_syms.c:62:1: warning: pasting "(" and "ftape_seek_to_eot" does not
give a valid preprocessing token
ftape_syms.c:63:1: warning: pasting "(" and "ftape_abort_operation" does not
give a valid preprocessing token
ftape_syms.c:64:1: warning: pasting "(" and "ftape_get_status" does not give
a valid preprocessing token
ftape_syms.c:65:1: warning: pasting "(" and "ftape_enable" does not give a
valid preprocessing token
ftape_syms.c:66:1: warning: pasting "(" and "ftape_disable" does not give a
valid preprocessing token
.
.
.
.
.
.
.
.
.
ftape_syms.c:94: (near initialization for
`__ksymtab_ftape_function_nest_level.value')
ftape_syms.c:95: `ftape_trace_call' undeclared here (not in a function)
ftape_syms.c:95: initializer element is not constant
ftape_syms.c:95: (near initialization for
`__ksymtab_ftape_trace_call.value')
ftape_syms.c:96: `ftape_trace_exit' undeclared here (not in a function)
ftape_syms.c:96: initializer element is not constant
ftape_syms.c:96: (near initialization for
`__ksymtab_ftape_trace_exit.value')
ftape_syms.c:97: `ftape_trace_log' undeclared here (not in a function)
ftape_syms.c:97: initializer element is not constant
ftape_syms.c:97: (near initialization for `__ksymtab_ftape_trace_log.value')
make[4]: *** [ftape_syms.o] Error 1
make[4]: Leaving directory
`/usr/src/linux-2.2.19/drivers/char/ftape/lowlevel'
make[3]: *** [_modsubdir_lowlevel] Error 2
make[3]: Leaving directory `/usr/src/linux-2.2.19/drivers/char/ftape'
make[2]: *** [_modsubdir_ftape] Error 2
make[2]: Leaving directory `/usr/src/linux-2.2.19/drivers/char'
make[1]: *** [_modsubdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.2.19/drivers'
make: *** [_mod_drivers] Error 2

You might try grepping the Makefiles in the linux source tree
for "traditional," some of the 2.2 Makefiles seem to use this, which
can cause those preprocessor errors. It is probably safe to just
remove "-traditional" from the Makefiles if that is the problem.

Lee