Re: [clamav-users] Problem configuring clamav-0.99
HI Steve/Todd i did it, of course by the help of mister Steve 1) i have installed the latest pcre from source pcre-8.36.tar.gz 2) find / -name libpcre.so.1 -print , i found it in (/usr/local/lib/libpcre.so.1) path 3) export LD_LIBRARY_PATH=/usr/local/lib and i' ve launched the configuration (./configure --disable-llvm --enable-check --enable-clamdtop --with-user=clamav --with-group=clamav --enable-experimental ) my configuration (and bingo no errors) ( this could eventually help for the case of mister Todd) thank you so much Steve/Todd bye -- ali atik > HI Steve, thanks for your reply. > > I did install a new version of PCRE to the directory /usr/local/pcre > (configured it with --prefix=/usr/local/prce so as to not interfere with > the older installed pcre), and told clamav's configure to use it with the > line --with-pcre=/usr/local/pcre. This is what got me to the "configure: > error: Structure packing seems to be available, but is not working with > this compiler", which is the same issue that ali atik is having. > > > > Todd A. Aiken > Systems Analyst & Administrator > ITS Department > BISHOP'S UNIVERSITY > 2600 College Street > Sherbrooke, Quebec > CANADA J1M 1Z7 > > > > > > > > > -Original Message- > From: clamav-users on behalf of > Steven Morgan > Reply-To: ClamAV users ML > Date: Wednesday, December 16, 2015 at 2:43 PM > To: ClamAV users ML > Subject: Re: [clamav-users] Problem configuring clamav-0.99 > >>Todd, >> >>PCRE support is new in ClamAV 0.99 and ./configure looks for it by >> default. >>So in your case it found an old version of pcre which is incompatible >> with >>ClamAV 0.99. Minimum PCRE version checks have been added for the upcoming >>0.99.1 release. For installing 0.99 on your system, you will either need >> to >>use './configure --with-pcre=no ...' or install a more current version of >>PCRE. >> >>Steve >> >>On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken >> wrote: >> >>> -----Original Message- >>> >>> >>> From: clamav-users on behalf of >>> " >>> a...@cerist.dz" >>> Reply-To: ClamAV users ML >>> Date: Monday, December 7, 2015 at 12:25 PM >>> To: ClamAV users ML >>> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >>> >>> >checking bzlib.h presence... yes >>> >checking for bzlib.h... yes >>> >checking for CVE-2008-1372... linkfailed >>> >configure: WARNING: ** Unable to link bzip2 testcase >>> >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, >>> but I >>> >need to be able to link a testcase to verify >>> >configure: WARNING: ** It is recommended to fix your build >>> environment >>> >so that we can run the testcase! >>> >configure: WARNING: ** Please do not report stability problems to >>> the >>> >ClamAV developers! >>> >checking for CVE-2010-0405... linkfailed >>> >configure: WARNING: ** Unable to link bzip2 testcase >>> >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, >>> but I >>> >need to be able to link a testcase to verify >>> >configure: WARNING: ** It is recommended to fix your build >>> environment >>> >so that we can run the testcase! >>> >configure: WARNING: ** Please do not report stability problems to >>> the >>> >ClamAV developers! >>> >checking for getaddrinfo... no >>> >>> -snip- >>> >>> >checking for type aligning via __attribute__((aligned))... yes >>> >checking that structure packing works... no >>> >configure: error: Structure packing seems to be available, but is not >>> >working with this compiler >>> >>> I am having the exact same issue with trying to compile on an old >>> Slackware server (running Slackware 10.2.0). I had to install an >>> updated >>> version of pcre in order to get past a different compiling issue, and >>> installed the new version to /usr/local/pcre with the configure >>> parameter >>> --prefix=/usr/local/pcre, but when I try to configure clamav-0.99 using >>> --with-pcre=/usr/local/pcre, I get this same structure error. Here is >>> the >>> full configure line I am using for clamav-0.99: >>> >>> ./configure --prefix=/usr --sysconfdir=/etc --disable-llvm >>> --disable-ipv6 >>> --with-openssl=/us
Re: [clamav-users] Problem configuring clamav-0.99
> Ali, Hi Stiven and thank you so much for your replay, and Todd for his participation too > > Please look in your config.log file for Structure packing. Do you have the > same or similar error? > > configure:20381: checking that structure packing works > configure:20438: gcc -o conftest -g -O2 -I/opt/pcre837/include > -L/opt/pcre837/lib -lpcre conftest.c -ldl >&5 > conftest.c:147: warning: 'packed' attribute ignored for field of type > 'char' > configure:20438: $? = 0 > configure:20438: ./conftest > ./conftest: error while loading shared libraries: libpcre.so.1: cannot > open > shared object file: No such file or directory and this is my required config.log lines : ... configure:20381: checking that structure packing works configure:20438: gcc -o conftest -g -O2 -fno-strict-aliasing -I/usr/local/include -L/usr/local/lib -lpcre conftest.c -ldl >&5 conftest.c:147: warning: 'packed' attribute ignored for field of type 'char' configure:20438: $? = 0 configure:20438: ./conftest ./conftest: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory configure:20438: $? = 127 ... > > This is the conftest for "structure packing" failing because it cannot > link > to the pcre shared library. If this is the case, I can suggest looking > into > using ldconfig or setting the environment variable LD_LIBRARY_PATH to > resolve the link issue, and then configure ClamAV. i will dig into this -- ali > > Hope this helps, > Steve > > On Wed, Dec 16, 2015 at 3:00 PM, Steven Morgan > wrote: > >> Ali / Todd, >> >> Thanks for the updates, I am looking into what is the possible cause for >> the "Structure packing" error. >> >> What are your compiler versions? >> >> Steve >> >> On Wed, Dec 16, 2015 at 2:53 PM, Todd Aiken >> wrote: >> >>> HI Steve, thanks for your reply. >>> >>> I did install a new version of PCRE to the directory /usr/local/pcre >>> (configured it with --prefix=/usr/local/prce so as to not interfere >>> with >>> the older installed pcre), and told clamav's configure to use it with >>> the >>> line --with-pcre=/usr/local/pcre. This is what got me to the >>> "configure: >>> error: Structure packing seems to be available, but is not working with >>> this compiler", which is the same issue that ali atik is having. >>> >>> >>> >>> Todd A. Aiken >>> Systems Analyst & Administrator >>> ITS Department >>> BISHOP'S UNIVERSITY >>> 2600 College Street >>> Sherbrooke, Quebec >>> CANADA J1M 1Z7 >>> >>> >>> >>> >>> >>> >>> >>> >>> -Original Message- >>> From: clamav-users on behalf of >>> Steven Morgan >>> Reply-To: ClamAV users ML >>> Date: Wednesday, December 16, 2015 at 2:43 PM >>> To: ClamAV users ML >>> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >>> >>> >Todd, >>> > >>> >PCRE support is new in ClamAV 0.99 and ./configure looks for it by >>> default. >>> >So in your case it found an old version of pcre which is incompatible >>> with >>> >ClamAV 0.99. Minimum PCRE version checks have been added for the >>> upcoming >>> >0.99.1 release. For installing 0.99 on your system, you will either >>> need >>> to >>> >use './configure --with-pcre=no ...' or install a more current version >>> of >>> >PCRE. >>> > >>> >Steve >>> > >>> >On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken >>> wrote: >>> > >>> >> -Original Message- >>> >> >>> >> >>> >> From: clamav-users on behalf >>> of " >>> >> a...@cerist.dz" >>> >> Reply-To: ClamAV users ML >>> >> Date: Monday, December 7, 2015 at 12:25 PM >>> >> To: ClamAV users ML >>> >> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >>> >> >>> >> >checking bzlib.h presence... yes >>> >> >checking for bzlib.h... yes >>> >> >checking for CVE-2008-1372... linkfailed >>> >> >configure: WARNING: ** Unable to link bzip2 testcase >>> >> >configure: WARNING: ** You may be affected by CVE-2008-1372 >>> bug, >>> but
Re: [clamav-users] Problem configuring clamav-0.99
Ali, Please look in your config.log file for Structure packing. Do you have the same or similar error? configure:20381: checking that structure packing works configure:20438: gcc -o conftest -g -O2 -I/opt/pcre837/include -L/opt/pcre837/lib -lpcre conftest.c -ldl >&5 conftest.c:147: warning: 'packed' attribute ignored for field of type 'char' configure:20438: $? = 0 configure:20438: ./conftest ./conftest: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory This is the conftest for "structure packing" failing because it cannot link to the pcre shared library. If this is the case, I can suggest looking into using ldconfig or setting the environment variable LD_LIBRARY_PATH to resolve the link issue, and then configure ClamAV. Hope this helps, Steve On Wed, Dec 16, 2015 at 3:00 PM, Steven Morgan wrote: > Ali / Todd, > > Thanks for the updates, I am looking into what is the possible cause for > the "Structure packing" error. > > What are your compiler versions? > > Steve > > On Wed, Dec 16, 2015 at 2:53 PM, Todd Aiken > wrote: > >> HI Steve, thanks for your reply. >> >> I did install a new version of PCRE to the directory /usr/local/pcre >> (configured it with --prefix=/usr/local/prce so as to not interfere with >> the older installed pcre), and told clamav's configure to use it with the >> line --with-pcre=/usr/local/pcre. This is what got me to the "configure: >> error: Structure packing seems to be available, but is not working with >> this compiler", which is the same issue that ali atik is having. >> >> >> >> Todd A. Aiken >> Systems Analyst & Administrator >> ITS Department >> BISHOP'S UNIVERSITY >> 2600 College Street >> Sherbrooke, Quebec >> CANADA J1M 1Z7 >> >> >> >> >> >> >> >> >> -Original Message- >> From: clamav-users on behalf of >> Steven Morgan >> Reply-To: ClamAV users ML >> Date: Wednesday, December 16, 2015 at 2:43 PM >> To: ClamAV users ML >> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >> >> >Todd, >> > >> >PCRE support is new in ClamAV 0.99 and ./configure looks for it by >> default. >> >So in your case it found an old version of pcre which is incompatible >> with >> >ClamAV 0.99. Minimum PCRE version checks have been added for the upcoming >> >0.99.1 release. For installing 0.99 on your system, you will either need >> to >> >use './configure --with-pcre=no ...' or install a more current version of >> >PCRE. >> > >> >Steve >> > >> >On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken >> wrote: >> > >> >> -Original Message- >> >> >> >> >> >> From: clamav-users on behalf >> of " >> >> a...@cerist.dz" >> >> Reply-To: ClamAV users ML >> >> Date: Monday, December 7, 2015 at 12:25 PM >> >> To: ClamAV users ML >> >> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >> >> >> >> >checking bzlib.h presence... yes >> >> >checking for bzlib.h... yes >> >> >checking for CVE-2008-1372... linkfailed >> >> >configure: WARNING: ** Unable to link bzip2 testcase >> >> >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, >> but I >> >> >need to be able to link a testcase to verify >> >> >configure: WARNING: ** It is recommended to fix your build >> environment >> >> >so that we can run the testcase! >> >> >configure: WARNING: ** Please do not report stability problems to >> the >> >> >ClamAV developers! >> >> >checking for CVE-2010-0405... linkfailed >> >> >configure: WARNING: ** Unable to link bzip2 testcase >> >> >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, >> but I >> >> >need to be able to link a testcase to verify >> >> >configure: WARNING: ** It is recommended to fix your build >> environment >> >> >so that we can run the testcase! >> >> >configure: WARNING: ** Please do not report stability problems to >> the >> >> >ClamAV developers! >> >> >checking for getaddrinfo... no >> >> >> >> -snip- >> >> >> >> >checking for type aligning via __attribute__((aligned))... yes >&g
Re: [clamav-users] Problem configuring clamav-0.99
Ali / Todd, Thanks for the updates, I am looking into what is the possible cause for the "Structure packing" error. What are your compiler versions? Steve On Wed, Dec 16, 2015 at 2:53 PM, Todd Aiken wrote: > HI Steve, thanks for your reply. > > I did install a new version of PCRE to the directory /usr/local/pcre > (configured it with --prefix=/usr/local/prce so as to not interfere with > the older installed pcre), and told clamav's configure to use it with the > line --with-pcre=/usr/local/pcre. This is what got me to the "configure: > error: Structure packing seems to be available, but is not working with > this compiler", which is the same issue that ali atik is having. > > > > Todd A. Aiken > Systems Analyst & Administrator > ITS Department > BISHOP'S UNIVERSITY > 2600 College Street > Sherbrooke, Quebec > CANADA J1M 1Z7 > > > > > > > > > -Original Message- > From: clamav-users on behalf of > Steven Morgan > Reply-To: ClamAV users ML > Date: Wednesday, December 16, 2015 at 2:43 PM > To: ClamAV users ML > Subject: Re: [clamav-users] Problem configuring clamav-0.99 > > >Todd, > > > >PCRE support is new in ClamAV 0.99 and ./configure looks for it by > default. > >So in your case it found an old version of pcre which is incompatible with > >ClamAV 0.99. Minimum PCRE version checks have been added for the upcoming > >0.99.1 release. For installing 0.99 on your system, you will either need > to > >use './configure --with-pcre=no ...' or install a more current version of > >PCRE. > > > >Steve > > > >On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken > wrote: > > > >> -Original Message----- > >> > >> > >> From: clamav-users on behalf > of " > >> a...@cerist.dz" > >> Reply-To: ClamAV users ML > >> Date: Monday, December 7, 2015 at 12:25 PM > >> To: ClamAV users ML > >> Subject: Re: [clamav-users] Problem configuring clamav-0.99 > >> > >> >checking bzlib.h presence... yes > >> >checking for bzlib.h... yes > >> >checking for CVE-2008-1372... linkfailed > >> >configure: WARNING: ** Unable to link bzip2 testcase > >> >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, > but I > >> >need to be able to link a testcase to verify > >> >configure: WARNING: ** It is recommended to fix your build > environment > >> >so that we can run the testcase! > >> >configure: WARNING: ** Please do not report stability problems to > the > >> >ClamAV developers! > >> >checking for CVE-2010-0405... linkfailed > >> >configure: WARNING: ** Unable to link bzip2 testcase > >> >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, > but I > >> >need to be able to link a testcase to verify > >> >configure: WARNING: ** It is recommended to fix your build > environment > >> >so that we can run the testcase! > >> >configure: WARNING: ** Please do not report stability problems to > the > >> >ClamAV developers! > >> >checking for getaddrinfo... no > >> > >> -snip- > >> > >> >checking for type aligning via __attribute__((aligned))... yes > >> >checking that structure packing works... no > >> >configure: error: Structure packing seems to be available, but is not > >> >working with this compiler > >> > >> I am having the exact same issue with trying to compile on an old > >> Slackware server (running Slackware 10.2.0). I had to install an > updated > >> version of pcre in order to get past a different compiling issue, and > >> installed the new version to /usr/local/pcre with the configure > parameter > >> --prefix=/usr/local/pcre, but when I try to configure clamav-0.99 using > >> --with-pcre=/usr/local/pcre, I get this same structure error. Here is > the > >> full configure line I am using for clamav-0.99: > >> > >> ./configure --prefix=/usr --sysconfdir=/etc --disable-llvm > --disable-ipv6 > >> --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre > >> > >> Removing --with-pcre=/usr/local/pcre, configure completes successfully, > >> but then I get this when I run make: > >> > >> CC libclamav_la-matcher-pcre.lo > >> matcher-pcre.c: In function `cli_pcre_scanbuf': > >> matcher-pcre.c:740: error: `PCRE_ERROR_RECURSIONLIMIT' undeclared
Re: [clamav-users] Problem configuring clamav-0.99
HI Steve, thanks for your reply. I did install a new version of PCRE to the directory /usr/local/pcre (configured it with --prefix=/usr/local/prce so as to not interfere with the older installed pcre), and told clamav's configure to use it with the line --with-pcre=/usr/local/pcre. This is what got me to the "configure: error: Structure packing seems to be available, but is not working with this compiler", which is the same issue that ali atik is having. Todd A. Aiken Systems Analyst & Administrator ITS Department BISHOP'S UNIVERSITY 2600 College Street Sherbrooke, Quebec CANADA J1M 1Z7 -Original Message- From: clamav-users on behalf of Steven Morgan Reply-To: ClamAV users ML Date: Wednesday, December 16, 2015 at 2:43 PM To: ClamAV users ML Subject: Re: [clamav-users] Problem configuring clamav-0.99 >Todd, > >PCRE support is new in ClamAV 0.99 and ./configure looks for it by default. >So in your case it found an old version of pcre which is incompatible with >ClamAV 0.99. Minimum PCRE version checks have been added for the upcoming >0.99.1 release. For installing 0.99 on your system, you will either need to >use './configure --with-pcre=no ...' or install a more current version of >PCRE. > >Steve > >On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken wrote: > >> -Original Message- >> >> >> From: clamav-users on behalf of " >> a...@cerist.dz" >> Reply-To: ClamAV users ML >> Date: Monday, December 7, 2015 at 12:25 PM >> To: ClamAV users ML >> Subject: Re: [clamav-users] Problem configuring clamav-0.99 >> >> >checking bzlib.h presence... yes >> >checking for bzlib.h... yes >> >checking for CVE-2008-1372... linkfailed >> >configure: WARNING: ** Unable to link bzip2 testcase >> >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, but I >> >need to be able to link a testcase to verify >> >configure: WARNING: ** It is recommended to fix your build environment >> >so that we can run the testcase! >> >configure: WARNING: ** Please do not report stability problems to the >> >ClamAV developers! >> >checking for CVE-2010-0405... linkfailed >> >configure: WARNING: ** Unable to link bzip2 testcase >> >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, but I >> >need to be able to link a testcase to verify >> >configure: WARNING: ** It is recommended to fix your build environment >> >so that we can run the testcase! >> >configure: WARNING: ** Please do not report stability problems to the >> >ClamAV developers! >> >checking for getaddrinfo... no >> >> -snip- >> >> >checking for type aligning via __attribute__((aligned))... yes >> >checking that structure packing works... no >> >configure: error: Structure packing seems to be available, but is not >> >working with this compiler >> >> I am having the exact same issue with trying to compile on an old >> Slackware server (running Slackware 10.2.0). I had to install an updated >> version of pcre in order to get past a different compiling issue, and >> installed the new version to /usr/local/pcre with the configure parameter >> --prefix=/usr/local/pcre, but when I try to configure clamav-0.99 using >> --with-pcre=/usr/local/pcre, I get this same structure error. Here is the >> full configure line I am using for clamav-0.99: >> >> ./configure --prefix=/usr --sysconfdir=/etc --disable-llvm --disable-ipv6 >> --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre >> >> Removing --with-pcre=/usr/local/pcre, configure completes successfully, >> but then I get this when I run make: >> >> CC libclamav_la-matcher-pcre.lo >> matcher-pcre.c: In function `cli_pcre_scanbuf': >> matcher-pcre.c:740: error: `PCRE_ERROR_RECURSIONLIMIT' undeclared (first >> use in this function) >> matcher-pcre.c:740: error: (Each undeclared identifier is reported only >> once >> matcher-pcre.c:740: error: for each function it appears in.) >> make[4]: *** [libclamav_la-matcher-pcre.lo] Error 1 >> make[4]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' >> make[3]: *** [all-recursive] Error 1 >> make[3]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/usr/src/software/clamav-0.99' >> make: *** [all] Error 2 >> >> (This is with PCRE version 6.4 that came with Slackware 10.2.0) >> >> As with the original poster, clamav-0.98.7 compiled fine on this same >> server and is currently running there. >> ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problem configuring clamav-0.99
Todd, PCRE support is new in ClamAV 0.99 and ./configure looks for it by default. So in your case it found an old version of pcre which is incompatible with ClamAV 0.99. Minimum PCRE version checks have been added for the upcoming 0.99.1 release. For installing 0.99 on your system, you will either need to use './configure --with-pcre=no ...' or install a more current version of PCRE. Steve On Mon, Dec 7, 2015 at 1:25 PM, Todd Aiken wrote: > -Original Message- > > > From: clamav-users on behalf of " > a...@cerist.dz" > Reply-To: ClamAV users ML > Date: Monday, December 7, 2015 at 12:25 PM > To: ClamAV users ML > Subject: Re: [clamav-users] Problem configuring clamav-0.99 > > >checking bzlib.h presence... yes > >checking for bzlib.h... yes > >checking for CVE-2008-1372... linkfailed > >configure: WARNING: ** Unable to link bzip2 testcase > >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, but I > >need to be able to link a testcase to verify > >configure: WARNING: ** It is recommended to fix your build environment > >so that we can run the testcase! > >configure: WARNING: ** Please do not report stability problems to the > >ClamAV developers! > >checking for CVE-2010-0405... linkfailed > >configure: WARNING: ** Unable to link bzip2 testcase > >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, but I > >need to be able to link a testcase to verify > >configure: WARNING: ** It is recommended to fix your build environment > >so that we can run the testcase! > >configure: WARNING: ** Please do not report stability problems to the > >ClamAV developers! > >checking for getaddrinfo... no > > -snip- > > >checking for type aligning via __attribute__((aligned))... yes > >checking that structure packing works... no > >configure: error: Structure packing seems to be available, but is not > >working with this compiler > > I am having the exact same issue with trying to compile on an old > Slackware server (running Slackware 10.2.0). I had to install an updated > version of pcre in order to get past a different compiling issue, and > installed the new version to /usr/local/pcre with the configure parameter > --prefix=/usr/local/pcre, but when I try to configure clamav-0.99 using > --with-pcre=/usr/local/pcre, I get this same structure error. Here is the > full configure line I am using for clamav-0.99: > > ./configure --prefix=/usr --sysconfdir=/etc --disable-llvm --disable-ipv6 > --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre > > Removing --with-pcre=/usr/local/pcre, configure completes successfully, > but then I get this when I run make: > > CC libclamav_la-matcher-pcre.lo > matcher-pcre.c: In function `cli_pcre_scanbuf': > matcher-pcre.c:740: error: `PCRE_ERROR_RECURSIONLIMIT' undeclared (first > use in this function) > matcher-pcre.c:740: error: (Each undeclared identifier is reported only > once > matcher-pcre.c:740: error: for each function it appears in.) > make[4]: *** [libclamav_la-matcher-pcre.lo] Error 1 > make[4]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/src/software/clamav-0.99' > make: *** [all] Error 2 > > (This is with PCRE version 6.4 that came with Slackware 10.2.0) > > As with the original poster, clamav-0.98.7 compiled fine on this same > server and is currently running there. > > > Thanks. > > > Todd A. Aiken > Systems Analyst & Administrator > ITS Department > BISHOP'S UNIVERSITY > 2600 College Street > Sherbrooke, Quebec > CANADA J1M 1Z7 > > > > ___ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problem configuring clamav-0.99
> bzip2 1.0.5 looks kind of old. Can you try a more current version? Hi Steven i dont think it is an bzip2 problem because when i have tried to configure my clamav without bzip2 (--disable-bzip2 option), i 've got nothing changed (same error) [root@mail clamav-0.99]# ./configure --disable-llvm --enable-check --enable-clamdtop --with-user=clamav --with-group=clamav --enable-experimental --disable-bzip2 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu creating target.h - canonical system defines checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no 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 dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -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 minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1966080 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) 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 for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes 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... no checking which extension is used for runtime loadable modules... .so checking which variable specifies run-time module search path... LD_LIBRARY_PATH checking for the default library search path... /lib /usr/lib /usr/lib/mysql /usr/lib/qt-3.3/lib /usr/lib/xulrunner checking for library containing dlopen... -ldl checking for dlerror... yes checking for shl_load... (cached) no checking for shl_load in -ldld... (cached) no checking for dld_link in -ldld... no checking for _ prefix in compiled symbols... no checking whether deplibs are l
Re: [clamav-users] Problem configuring clamav-0.99
bzip2 1.0.5 looks kind of old. Can you try a more current version? On Mon, Dec 7, 2015 at 12:25 PM, wrote: > > Hi Ali, > > > > Can you heck to see that you have installed the development versions of > > bzip2 and check rpms (bzip2-devel-*.rpm / check-devel-*rpm)? > > > > Steve > > Hi Steve, > > I have checked my installation, and yes the package check was installed > from source, the other package bzip2-devel was already installed: so i > have launched the installation of the package check from repository > now > i can say that both packages are there: > > [root@mail clamav-0.99]# rpm -q check check-devel > check-0.9.8-1.1.el6.i686 > check-devel-0.9.8-1.1.el6.i686 > > [root@mail clamav-0.99]# rpm -q bzip2 bzip2-devel > bzip2-1.0.5-7.el6_0.i686 > bzip2-devel-1.0.5-7.el6_0.i686 > > when i restarted the configuration the error regarding the check module > disappeared (bravo!) > > but unfortunately the second issue is always there as you can see below: > > [root@mail clamav-0.99]# ./configure --enable-llvm --enable-check > --enable-clamdtop --with-user=clamav --with-group=clamav > --enable-experimental > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > creating target.h - canonical system defines > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking how to create a ustar tar archive... gnutar > checking whether make supports nested variables... yes > checking for style of include used by make... GNU > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > 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 dependency style of gcc... gcc3 > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -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 minix/config.h usability... no > checking minix/config.h presence... no > checking for minix/config.h... no > checking whether it is safe to define __EXTENSIONS__... yes > checking how to print strings... printf > checking for a sed that does not truncate output... /bin/sed > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1966080 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu > format... func_convert_file_noop > checking how to convert i686-pc-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... no > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for mt... no > checking if : is a manifest tool... no > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... no > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) 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 for shl_load... no > checking for shl_load in -ldld... no > checking for dlopen... no > checking for dlopen in -
Re: [clamav-users] Problem configuring clamav-0.99
-Original Message- From: clamav-users on behalf of "a...@cerist.dz" Reply-To: ClamAV users ML Date: Monday, December 7, 2015 at 12:25 PM To: ClamAV users ML Subject: Re: [clamav-users] Problem configuring clamav-0.99 >checking bzlib.h presence... yes >checking for bzlib.h... yes >checking for CVE-2008-1372... linkfailed >configure: WARNING: ** Unable to link bzip2 testcase >configure: WARNING: ** You may be affected by CVE-2008-1372 bug, but I >need to be able to link a testcase to verify >configure: WARNING: ** It is recommended to fix your build environment >so that we can run the testcase! >configure: WARNING: ** Please do not report stability problems to the >ClamAV developers! >checking for CVE-2010-0405... linkfailed >configure: WARNING: ** Unable to link bzip2 testcase >configure: WARNING: ** You may be affected by CVE-2010-0405 bug, but I >need to be able to link a testcase to verify >configure: WARNING: ** It is recommended to fix your build environment >so that we can run the testcase! >configure: WARNING: ** Please do not report stability problems to the >ClamAV developers! >checking for getaddrinfo... no -snip- >checking for type aligning via __attribute__((aligned))... yes >checking that structure packing works... no >configure: error: Structure packing seems to be available, but is not >working with this compiler I am having the exact same issue with trying to compile on an old Slackware server (running Slackware 10.2.0). I had to install an updated version of pcre in order to get past a different compiling issue, and installed the new version to /usr/local/pcre with the configure parameter --prefix=/usr/local/pcre, but when I try to configure clamav-0.99 using --with-pcre=/usr/local/pcre, I get this same structure error. Here is the full configure line I am using for clamav-0.99: ./configure --prefix=/usr --sysconfdir=/etc --disable-llvm --disable-ipv6 --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre Removing --with-pcre=/usr/local/pcre, configure completes successfully, but then I get this when I run make: CC libclamav_la-matcher-pcre.lo matcher-pcre.c: In function `cli_pcre_scanbuf': matcher-pcre.c:740: error: `PCRE_ERROR_RECURSIONLIMIT' undeclared (first use in this function) matcher-pcre.c:740: error: (Each undeclared identifier is reported only once matcher-pcre.c:740: error: for each function it appears in.) make[4]: *** [libclamav_la-matcher-pcre.lo] Error 1 make[4]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/software/clamav-0.99/libclamav' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/software/clamav-0.99' make: *** [all] Error 2 (This is with PCRE version 6.4 that came with Slackware 10.2.0) As with the original poster, clamav-0.98.7 compiled fine on this same server and is currently running there. Thanks. Todd A. Aiken Systems Analyst & Administrator ITS Department BISHOP'S UNIVERSITY 2600 College Street Sherbrooke, Quebec CANADA J1M 1Z7 ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problem configuring clamav-0.99
> Hi Ali, > > Can you heck to see that you have installed the development versions of > bzip2 and check rpms (bzip2-devel-*.rpm / check-devel-*rpm)? > > Steve Hi Steve, I have checked my installation, and yes the package check was installed from source, the other package bzip2-devel was already installed: so i have launched the installation of the package check from repository now i can say that both packages are there: [root@mail clamav-0.99]# rpm -q check check-devel check-0.9.8-1.1.el6.i686 check-devel-0.9.8-1.1.el6.i686 [root@mail clamav-0.99]# rpm -q bzip2 bzip2-devel bzip2-1.0.5-7.el6_0.i686 bzip2-devel-1.0.5-7.el6_0.i686 when i restarted the configuration the error regarding the check module disappeared (bravo!) but unfortunately the second issue is always there as you can see below: [root@mail clamav-0.99]# ./configure --enable-llvm --enable-check --enable-clamdtop --with-user=clamav --with-group=clamav --enable-experimental checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu creating target.h - canonical system defines checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no 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 dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -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 minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1966080 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) 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 for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes 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 librari
Re: [clamav-users] Problem configuring clamav-0.99
Hi Ali, Can you heck to see that you have installed the development versions of bzip2 and check rpms (bzip2-devel-*.rpm / check-devel-*rpm)? Steve On Mon, Dec 7, 2015 at 10:03 AM, wrote: > Hello everybody > > I am using Linux Centos6.7 (i686 ) > and i am using clamav as antivirus for my qmail server with other modules > > today when i was upgrading from clamav-0.98.7 to clamav-0.99 > > i got a configuration issue: > > > > [root@mail clamav-0.99]# ./configure --enable-llvm --enable-check > --enable-clamdtop --with-user=clamav --with-group=clamav > --enable-experimental > ... > ...(here i have I removed lines) > > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for shared library run path origin... done > checking check.h usability... yes > checking check.h presence... yes > checking for check.h... yes > checking linking with check... configure: unable to compile/link with check > configure: error: > > ERROR! Check was configured, but not found. Get it from > http://check.sf.net/ > > [root@mail clamav-0.99]# > > even though i have installed the check modules (check-0.10.0 ) > i still have the same complaining > > -- > i've tried to launch the configuration without the (--enable-check) option > > i have got another issue as you can see below > > [root@mail clamav-0.99]# ./configure --enable-llvm --enable-clamdtop > --with-user=clamav --with-group=clamav --enable-experimental > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > creating target.h - canonical system defines > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking how to create a ustar tar archive... gnutar > checking whether make supports nested variables... yes > checking for style of include used by make... GNU > checking for gcc... gcc > > .(here i have I removed lines) > > checking bzlib.h usability... yes > checking bzlib.h presence... yes > checking for bzlib.h... yes > checking for CVE-2008-1372... linkfailed > configure: WARNING: ** Unable to link bzip2 testcase > configure: WARNING: ** You may be affected by CVE-2008-1372 bug, but I > need to be able to link a testcase to verify > configure: WARNING: ** It is recommended to fix your build environment > so that we can run the testcase! > configure: WARNING: ** Please do not report stability problems to the > ClamAV developers! > checking for CVE-2010-0405... linkfailed > configure: WARNING: ** Unable to link bzip2 testcase > configure: WARNING: ** You may be affected by CVE-2010-0405 bug, but I > need to be able to link a testcase to verify > configure: WARNING: ** It is recommended to fix your build environment > so that we can run the testcase! > configure: WARNING: ** Please do not report stability problems to the > ClamAV developers! > checking for getaddrinfo... no > checking for IPv6 support... no > checking for resolv.h... yes > checking for dn_expand in std libs... no > checking for dn_expand in -lresolv... yes > checking whether setpgrp takes no argument... yes > checking for libiconv_open in -liconv... no > checking for iconv... yes > checking for pthread.h... (cached) yes > checking whether in_port_t is defined... yes > checking for in_addr_t definition... yes > checking sys/fanotify.h usability... no > checking sys/fanotify.h presence... no > checking for sys/fanotify.h... no > checking for sched_yield... yes > checking for pthread_yield... yes > checking for readdir_r... support disabled > checking for ctime_r... yes, and it takes 2 arguments > checking for socklen_t... yes > checking for structure packing via __attribute__((packed))... yes > checking for type aligning via __attribute__((aligned))... yes > checking that structure packing works... no > configure: error: Structure packing seems to be available, but is not > working with this compiler > [root@mail clamav-0.99]# > > and yes bzip2 is installed too > > what seems to be wrong with my system, knowing that the previous > installation(clamav-0.98.7) worked well with the same configuration. > > i will appreciate any help from any body here -- > thank you for your time in advance.. > (and sorry for my poor english too) > > -- > ali atik > > > > > > > > > > ___ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
[clamav-users] Problem configuring clamav-0.99
Hello everybody I am using Linux Centos6.7 (i686 ) and i am using clamav as antivirus for my qmail server with other modules today when i was upgrading from clamav-0.98.7 to clamav-0.99 i got a configuration issue: [root@mail clamav-0.99]# ./configure --enable-llvm --enable-check --enable-clamdtop --with-user=clamav --with-group=clamav --enable-experimental ... ...(here i have I removed lines) checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking check.h usability... yes checking check.h presence... yes checking for check.h... yes checking linking with check... configure: unable to compile/link with check configure: error: ERROR! Check was configured, but not found. Get it from http://check.sf.net/ [root@mail clamav-0.99]# even though i have installed the check modules (check-0.10.0 ) i still have the same complaining -- i've tried to launch the configuration without the (--enable-check) option i have got another issue as you can see below [root@mail clamav-0.99]# ./configure --enable-llvm --enable-clamdtop --with-user=clamav --with-group=clamav --enable-experimental checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu creating target.h - canonical system defines checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for gcc... gcc .(here i have I removed lines) checking bzlib.h usability... yes checking bzlib.h presence... yes checking for bzlib.h... yes checking for CVE-2008-1372... linkfailed configure: WARNING: ** Unable to link bzip2 testcase configure: WARNING: ** You may be affected by CVE-2008-1372 bug, but I need to be able to link a testcase to verify configure: WARNING: ** It is recommended to fix your build environment so that we can run the testcase! configure: WARNING: ** Please do not report stability problems to the ClamAV developers! checking for CVE-2010-0405... linkfailed configure: WARNING: ** Unable to link bzip2 testcase configure: WARNING: ** You may be affected by CVE-2010-0405 bug, but I need to be able to link a testcase to verify configure: WARNING: ** It is recommended to fix your build environment so that we can run the testcase! configure: WARNING: ** Please do not report stability problems to the ClamAV developers! checking for getaddrinfo... no checking for IPv6 support... no checking for resolv.h... yes checking for dn_expand in std libs... no checking for dn_expand in -lresolv... yes checking whether setpgrp takes no argument... yes checking for libiconv_open in -liconv... no checking for iconv... yes checking for pthread.h... (cached) yes checking whether in_port_t is defined... yes checking for in_addr_t definition... yes checking sys/fanotify.h usability... no checking sys/fanotify.h presence... no checking for sys/fanotify.h... no checking for sched_yield... yes checking for pthread_yield... yes checking for readdir_r... support disabled checking for ctime_r... yes, and it takes 2 arguments checking for socklen_t... yes checking for structure packing via __attribute__((packed))... yes checking for type aligning via __attribute__((aligned))... yes checking that structure packing works... no configure: error: Structure packing seems to be available, but is not working with this compiler [root@mail clamav-0.99]# and yes bzip2 is installed too what seems to be wrong with my system, knowing that the previous installation(clamav-0.98.7) worked well with the same configuration. i will appreciate any help from any body here -- thank you for your time in advance.. (and sorry for my poor english too) -- ali atik ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
