i want to protect my filesever with avast4guard
but there is a problem.
when i start the ./configure script then i get the following error.
asterisk:/home/marco/avast4guard-3.0.1# ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
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 ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for correct ltmain.sh version... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for strip... (cached) strip
checking whether to turn on debugging... no
checking for getopt_long... yes
checking whether struct sockaddr_in6 is in netinet/in.h... yes
checking for ar... ar
checking for gzip... gzip
checking for tar... tar
checking for rpm... no
checking for rpmbuild... no
checking for ebuild... no
checking for makepkg... no
checking for pkgmk... no
checking for gpg... gpg
checking for a BSD-compatible install... /usr/bin/install -c
checking for nm... /usr/bin/nm -B
checking for printf in -lc... yes
checking for gethostbyname... yes
checking for gethostbyname2... yes
checking dazukoio.h usability... no
checking dazukoio.h presence... no
checking for dazukoio.h... no
configure: error: required library and/or header file not found, install Dazuko 2.1.0 or higher
I have sucsessfull installed the dazukofs-3.0.0-rc4_2.6.26.tar.gz paket from the antivir_workstation-pers305 archive.
(located in contrib folder) this is the only version that can compile under debian lenny kernel 2.6.26
asterisk:/home/marco/avast4guard-3.0.1# lsmod
Module Size Used by
dazukofs 27992 0
snd_seq_dummy 2660 0
appletalk 26016 20
nfsd 186864 13
lockd 54568 1 nfsd
nfs_acl 2912 1 nfsd
auth_rpcgss 33952 1 nfsd
sunrpc 162528 11 nfsd,lockd,nfs_acl,auth_rpcgss
exportfs 3936 1 nfsd
ppdev 6468 0
lp 8164 0
ipv6 235396 39
tun 8292 2
ztdummy 3120 0
zaptel 184036 3 ztdummy
crc_ccitt 2080 1 zaptel
loop 12748 0
mISDN_dsp 189576 1
hfcmulti 65324 1
l3udss1 33340 1
mISDN_l2 30900 1
mISDN_l1 8988 1
parport_pc 22500 1
parport 30988 3 ppdev,lp,parport_pc
i2c_i801 7920 0
pcspkr 2432 0
i2c_core 19828 1 i2c_i801
mISDN_core 69536 5 mISDN_dsp,hfcmulti,l3udss1,mISDN_l2,mISDN_l1
rng_core 3940 0
atl2 22744 0
snd_hda_intel 325688 0
snd_pcm 62660 1 snd_hda_intel
snd_seq 41456 1 snd_seq_dummy
snd_timer 17800 2 snd_pcm,snd_seq
snd_seq_device 6380 2 snd_seq_dummy,snd_seq
intel_agp 22524 1
agpgart 28808 1 intel_agp
button 6096 0
snd 45636 5 snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device
soundcore 6368 1 snd
snd_page_alloc 7816 2 snd_hda_intel,snd_pcm
evdev 8000 0
ext3 105576 2
jbd 39476 1 ext3
mbcache 7108 1 ext3
sg 26964 0
sr_mod 13316 0
cdrom 30176 1 sr_mod
sd_mod 22200 5
ide_pci_generic 3908 0 [permanent]
usbhid 35904 1
hid 33184 1 usbhid
ff_memless 4392 1 usbhid
ata_piix 14180 3
piix 6568 0 [permanent]
ide_core 96168 2 ide_pci_generic,piix
8139cp 16800 0
ata_generic 4676 0
libata 140448 2 ata_piix,ata_generic
scsi_mod 129548 4 sg,sr_mod,sd_mod,libata
dock 8304 1 libata
8139too 20384 0
mii 4896 2 8139cp,8139too
ehci_hcd 28428 0
uhci_hcd 18672 0
usbcore 118192 5 usbhid,ehci_hcd,uhci_hcd
thermal 15228 0
processor 32576 1 thermal
fan 4196 0
thermal_sys 10856 3 thermal,processor,fan
is it possible to patch the configure script, so that avast4guard compile and run with dazukofs 3.x.x???