HarveyTitanium
12.05.2009 01:53
Any ideas?
Thanks, Harvey Titanium
cvs:/ # uname -a
Linux cvs 2.6.16.60-0.21-smp #1 SMP Tue May 6 12:41:02 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux
cvs:/ # /opt/kaspersky/kav4fs/src/kavmon.pl -b=/usr/src/linux-2.6.16.60-0.21
=== Configure kernel module using kernel sources from /usr/src/linux-2.6.16.60-0.21
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for linux kernel sources... /usr/src/linux-2.6.16.60-0.21
checking for linux kernel version file... /usr/src/linux-2.6.16.60-0.21/include/linux/version.h
checking for linux kernel version... 2.6
checking for linux/syscalls.h... yes
checking for module arch... 64
checking for sys_call_table... found, address 0xffffffff802f4ea0
checking for sys_call_table readonly... yes
checking for ia32_sys_call_table... found, address 0xffffffff802f5cd0
checking for ia32_sys_call_table readonly... yes
checking for tasklist_lock... "not exported"
checking for tasklist_lock... found, address 0xffffffff803df000
checking for __d_path... "not exported"
checking for vfsmount_lock... found, address 0xffffffff803e7e00
configure: creating ./config.status
config.status: creating Makefile
config.status: creating kavmon.h
config.status: creating osdef.h
config.status: creating module.linux/Makefile
=== Compiling Linux kernel module
Cleaning module.linux
make[1]: Entering directory `/opt/kaspersky/kav4fs/src/module.linux'
rm -f **.o *.ko ../bin//kavmon.ko monitor_helpers.c kernel.c queue.c md5.c cache.c util.c cache.h kavmon.h kernel.h md5.h monitor.h monitor_helpers.h osdef.h queue.h util.h *.mod.c .*.cmd Makefile.in
make[1]: Leaving directory `/opt/kaspersky/kav4fs/src/module.linux'
Making link in module.linux
make[1]: Entering directory `/opt/kaspersky/kav4fs/src/module.linux'
make -C /usr/src/linux-2.6.16.60-0.21 SUBDIRS=/opt/kaspersky/kav4fs/src/module.linux modules
make[2]: Entering directory `/usr/src/linux-2.6.16.60-0.21'
Makefile:450: .config: No such file or directory
WARNING: Symbol version dump /usr/src/linux-2.6.16.60-0.21/Module.symvers
is missing; modules will have no dependencies and modversions.
ln: creating symbolic link `./Makefile.lib.c' to `../scripts/Makefile.lib.c': File exists
make[3]: *** [scripts/Makefile.lib.c] Error 1
make[2]: *** [_module_/opt/kaspersky/kav4fs/src/module.linux] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.16.60-0.21'
make[1]: *** [kavmon_build] Error 2
make[1]: Leaving directory `/opt/kaspersky/kav4fs/src/module.linux'
make: *** [all] Error 1
kavmon module compilation error
cvs:/ #
In some linux kernels LSM were converted into static modules, so there is no such API anymore. I do not remember exactly in the meantime if they have already reverted it back by kernel version 2.6.27. As far as I remember, even if they reverted it, they simply have broken compatibility with older API... (thx 2 hinote

)
You may find further information here:
http://support.kaspersky.com/linux_file57/...r?qid=208280104http://forum.kaspersky.com/index.php?showt...5&hl=kavmonhttp://forum.kaspersky.com/index.php?showt...0&hl=kavmon
HarveyTitanium
12.05.2009 19:05
I find that answer very strange. Kaspersky states that SLES 10 SP2 - 32 and 64 bit are supported.
Software requirements:
One of the following operating systems for 32-bit platforms:
SUSE Linux Enterprise Server 10 SP2
One of the following operating systems for 64-bit platforms:
SUSE Linux Enterprise Server 10 SP2
That is from page 9 of kav5.7_linuxfsen
I am using the kernel off the install disk, no updates. This system is unmodified.
Harvey Titanium
Ooops... you're right. Mea culpa...
I'm going to test this on my virtual machine...
hi there,
try to configure the kernel in /usr/src/linux-<version> or copy existing kernel config file from /boot into your /usr/src/linux-<version>
CODE
# cp /boot/config-<blah-blah> /usr/src/linux-<version>/.config
P.S. in the kernel configuration, enable the Loadable kernel modules support if disabled
HarveyTitanium
19.05.2009 19:25
QUOTE(hinote @ 14.05.2009 04:04)

hi there,
try to configure the kernel in /usr/src/linux-<version> or copy existing kernel config file from /boot into your /usr/src/linux-<version>
CODE
# cp /boot/config-<blah-blah> /usr/src/linux-<version>/.config
P.S. in the kernel configuration, enable the Loadable kernel modules support if disabled
That got rid of "Makefile:450: .config: No such file or directory"
But still have the Symbol version error.
- HT
HarveyTitanium
19.05.2009 19:35
Getting closer. Had to copy Modules.symver from the linux-obj dir to the true source dir.
cvs:/usr/src/linux-obj/x86_64/default # cp Module.symvers /usr/src/linux-2.6.16.60-0.21
Next error.
=== Compiling Linux kernel module
Cleaning module.linux
make[1]: Entering directory `/opt/kaspersky/kav4fs/src/module.linux'
rm -f **.o *.ko ../bin//kavmon.ko monitor_helpers.c kernel.c queue.c md5.c cache.c util.c cache.h kavmon.h kernel.h md5.h monitor.h monitor_helpers.h osdef.h queue.h util.h *.mod.c .*.cmd Makefile.in
make[1]: Leaving directory `/opt/kaspersky/kav4fs/src/module.linux'
Making link in module.linux
make[1]: Entering directory `/opt/kaspersky/kav4fs/src/module.linux'
make -C /usr/src/linux-2.6.16.60-0.21/ SUBDIRS=/opt/kaspersky/kav4fs/src/module.linux modules
make[2]: Entering directory `/usr/src/linux-2.6.16.60-0.21'
ln: creating symbolic link `./Makefile.lib.c' to `../scripts/Makefile.lib.c': File exists
make[3]: *** [scripts/Makefile.lib.c] Error 1
make[2]: *** [_module_/opt/kaspersky/kav4fs/src/module.linux] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.16.60-0.21'
make[1]: *** [kavmon_build] Error 2
make[1]: Leaving directory `/opt/kaspersky/kav4fs/src/module.linux'
make: *** [all] Error 1
kavmon module compilation error
QUOTE(HarveyTitanium @ 19.05.2009 20:35)

ln: creating symbolic link `./Makefile.lib.c' to `../scripts/Makefile.lib.c': File exists
what about
make clean (or even distclean)
make
instead of single make?
bookleech
8.06.2009 04:11
ln: creating symbolic link `./Makefile.lib.c' to `../scripts/Makefile.lib.c': File exists
I've got the same problem on SLES 10 SP2 32-bit
"make clean" makes no difference ...
after "make distclean" kernel sources dont compile at all
bookleech
8.06.2009 10:55
I have also noticed that kavmon.pl tries to make symlinks to non-existing files (Makefile.lib.c instead of Makefile.lib, KBuild.include.c instead of Kbuild.include, etc. )
bookleech
9.06.2009 06:07
The problem was solved by running the kavmon.pl script from shell, not from Midnught Commander. The .c extension was somehow added to every filename when running Perl script from mc
to HarveyTitanium:
You dont have to copy Module.symvers. Install rpm package kernel-syms instead.
HarveyTitanium
9.06.2009 17:40
QUOTE(bookleech @ 8.06.2009 20:07)

The problem was solved by running the kavmon.pl script from shell, not from Midnught Commander. The .c extension was somehow added to every filename when running Perl script from mc
to HarveyTitanium:
You dont have to copy Module.symvers. Install rpm package kernel-syms instead.
I did have kernel-syms installed. Also, I have never use Midnight Commander, I am doing it all from the command line.
HT
HarveyTitanium
11.06.2009 01:36
QUOTE(HarveyTitanium @ 9.06.2009 07:40)

I did have kernel-syms installed. Also, I have never use Midnight Commander, I am doing it all from the command line.
HT
Ok, I got it figured out. I forgot to run the postinstall.pl script, once I did that everything fell into place.
HT
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.