Tried to compile 0.9.0 with kernel 2.4.6 on a RH7.1 machine with the latest gcc updates installed. gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o sysctl.o sysctl.c sysctl.c:317: `journal_oom_retry' undeclared here (not in a function) sysctl.c:317: initializer element is not constant sysctl.c:317: (near initialization for `fs_table[14].data') make[2]: *** [sysctl.o] Error 1 Klaasjan Brand kjb@dds.nl
Klaasjan Brand wrote:> > Tried to compile 0.9.0 with kernel 2.4.6 on a RH7.1 machine with the > latest gcc updates installed. > > gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes > -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -march=k6 -c -o sysctl.o sysctl.c > sysctl.c:317: `journal_oom_retry' undeclared here (not in a function) > sysctl.c:317: initializer element is not constant > sysctl.c:317: (near initialization for `fs_table[14].data') > make[2]: *** [sysctl.o] Error 1Damn. I forgot to rediff it. Please enable `JBD debugging support' in config.
Klaasjan Brand wrote:> > Tried to compile 0.9.0 with kernel 2.4.6 on a RH7.1 machine with the > latest gcc updates installed. > > gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes > -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -march=k6 -c -o sysctl.o sysctl.c > sysctl.c:317: `journal_oom_retry' undeclared here (not in a function) > sysctl.c:317: initializer element is not constant > sysctl.c:317: (near initialization for `fs_table[14].data') > make[2]: *** [sysctl.o] Error 1Actually, the patch was generated OK. The build failure occurs when ext3 is *disabled* in config. Sigh. Please enable ext3 in the filesystems menu.
> Actually, the patch was generated OK. The build failure occurs when > ext3 is *disabled* in config. Sigh.>Please enable ext3 in the filesystems menu.Ahem... CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_JBD_DEBUG=y # CONFIG_BUFFER_DEBUG is not set Seems _enabled_ to me... Klaasjan Brand kjb@dds.nl
Klaasjan Brand wrote:> > > Actually, the patch was generated OK. The build failure occurs when > > ext3 is *disabled* in config. Sigh. > > >Please enable ext3 in the filesystems menu. > > Ahem... > > CONFIG_EXT3_FS=y > CONFIG_JBD=y > CONFIG_JBD_DEBUG=y > # CONFIG_BUFFER_DEBUG is not set > > Seems _enabled_ to me... >In that case I have no explanation :( Could I suggest that you start afresh with the patch and build process?