Re: mount with cloop-2 on 2.6.x kernel problem

Yann Cochard <[email protected]>
Newsgroups gmane.linux.debian.knoppix
Message-ID <[email protected]>
Le samedi 1 Mai 2004 10:31, Rene Cunningham a écrit :
> > <command line>:138832141:26960:
> > /usr/src/linux/include/linux/modversions.h: No such file or directory
>
> Im running 2.6.5-mm6 and modversions.h lives in
> include/config/modversions.h not include/linux/modversions.h.
>
> Make a soft link or fix the Makefile for the cloop source.

Thanks. It now goes further: it generates the cloop.o file, but with warnings,
and after that it does not work (see below all the error messages).
The insmod command outputs an error : "Unknown symbol in module" (see below).
zlib.h was missing, so I installed the package zlib1-devel.

Thanks for your help, we are near the goal now ;-)

Yann



[[email protected] cloop-2.01]# make KERNEL_DIR=/usr/src/linux
cc -I/usr/src/linux/include -I/usr/src/linux/include/asm/mach-default  
-D__KERNEL__ -DMODULE -fno-builtin -nostdlib -DKBUILD_MODNAME="cloop" 
-DKBUILD_BASENAME="cloop" -DMODVERSIONS 
-include /usr/src/linux/include/linux/modversions.h compressed_loop.c -c -o 
compressed_loop.o
compressed_loop.c:880: warning: parameter names (without types) in function 
declaration
compressed_loop.c:880: warning: data definition has no type or storage class
compressed_loop.c:881: warning: parameter names (without types) in function 
declaration
compressed_loop.c:881: warning: data definition has no type or storage class
ld -r -o cloop.o compressed_loop.o
cc    -c -o create_compressed_fs.o create_compressed_fs.c
cc -o create_compressed_fs create_compressed_fs.o -lz
cc    -c -o extract_compressed_fs.o extract_compressed_fs.c
cc -o extract_compressed_fs extract_compressed_fs.o -lz

[[email protected] kla]# insmod cloop-2.01/cloop.o file=`pwd`/mnt/KNOPPIX/KNOPPIX
insmod: error inserting 'cloop-2.01/cloop.o': -1 Unknown symbol in module
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.