Skip to contentSkip to conversation

More problems with 2.5.0-pre5 than pre4

DISCUSSION Frank Jacobberger 2 participants 2 messages Dec 1, 2001 Block layer

lore
Share & tools
lore
#0 lore raw

What do you make of this from a attempted compile of 2.5.0-pre5:

gcc -D__KERNEL__ -I/usr/src/linux-2.5.0/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o rd.o rd.c
rd.c:561: `rd_cleanup' undeclared here (not in a function) make[3]: *** [rd.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.5.0/drivers/block' make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.5.0/drivers/block' make[1]: *** [_subdir_block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.0/drivers'
make: *** [_dir_drivers] Error 2

Thanks,

Frank

#1 lore raw

Frank Jacobberger <[email protected]> :

Quoted 1 line

What do you make of this from a attempted compile of 2.5.0-pre5:

[...]

drivers/block/rd.c +0 -2
diff -burN -p linux-2.5.1-pre5.orig/drivers/block/rd.c linux-2.5.1-pre5/drivers/block/rd.c
@@ -485,7 +485,6 @@ static struct block_device_operations rd
 	ioctl:		rd_ioctl,
 };
 
-#ifdef MODULE
 /* Before freeing the module, invalidate all of the protected buffers! */
 static void __exit rd_cleanup (void)
 {
@@ -503,7 +502,6 @@ static void __exit rd_cleanup (void)
 	unregister_blkdev( MAJOR_NR, "ramdisk" );
 	blk_clear(MAJOR_NR);
 }
-#endif
 
 /* This is the registration and initialization section of the RAM disk driver */
 int __init rd_init (void)