gcc 2.96 on Fedora Core 1

[Jakub Jelinek]

On Thu, Jun 17, 2004 at 06:37:03PM +0200, Flavius Copaciu wrote:
> 3.This one is inspired from an Oracle Application Server installation on 
> Fedora Core 1. Basically I have renamed gcc and g++ to gcc332 and g++332 
> and made symbolic links to gcc296 and g++296
> #mv /usr/bin/gcc /usr/bin/gcc332
> #mv /usr/bin/g++ /usr/bin/g++332
> #ln -s /usr/bin/gcc296 /usr/bin/gcc
> #ln -s /usr/bin/g++296 /usr/bin/g++
> Then a normal kernel compilation. But this does not help either.
> 
> 
> Ideas anyone?

gcc -D__KERNEL__ -I/usr/src/linux-2.4.22/include -Wall
-Wstrict-prototypes -Wno-trigra phs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack- boundary=2 -march=athlon
-nostdinc -iwithprefix include -DKBUILD_BASENAME=netsyms  -
DEXPORT_SYMTAB -c netsyms.c
netsyms.c:392: `ipv4_specific' undeclared here (not in a function)
netsyms.c:392: initializer element is not constant
netsyms.c:392: (near initialization for `__ksymtab_ipv4_specific.value')
make[2]: *** [netsyms.o] Error 1

I would certainly not start chasing an undeclared function problem by
trying a different compiler.

Instead, just grep for ipv4_specific in the headers and see why it is
not prototyped during your compilation.  Maybe you use some CONFIG_*
option mix others don't use or something and the symbol simply ends
up not prototyped or something.

	Jakub