[clamav-users] Compiling on x86_64 architecture
I am compiling 0.96.5 on RHEL 5, when I ran into this error during "make check". I realize this may not be a Clamav-specific bug, however it does involve a dependency. /usr/bin/ld: /usr/local/lib/libbz2.a(bzlib.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC I had to install a different version of libbz2 than what is provided with the OS. I compiled/installed with a simple "make install" which has worked fine on 32bit systems. I've never seen this problem before. Does anyone know how to solve this? I'm going to update the dev environment (yum update), then recompile libbz2 to see if that helps. Any pointers would be appreciated. Thanks. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[clamav-users] Compiling and installing from an NFS mount
I've run into a quirky issue with installing ClamAV from an NFS mount. I do this to keep the same code available to all my systems. I have separate mounts for 32- and 64-bit. For ClamAV, the installation will fail because the NFS mount itself is read-only (ro): make[3]: Entering directory `/local/dist/clamav/clamav-0.97.3/libclamav' GENversion.h.tmp rm: cannot remove `version.h.tmp': Read-only file system touch: cannot touch `version.h.tmp': Read-only file system Without digging into how this works, I believe I see what's going on -- but I wonder if there's a clever way around this. I really don't want to go through and change the mounts to read-write -- they are read-only for a reason -- or copy the code over and install each individually. Thanks. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Compiling and installing from an NFS mount
[ .. ] I do this to keep the same code available to all my systems. I have separate mounts for 32- and 64-bit. For something like ClamAV, I don't see the point. You seem to be making it harder for yourself than it needs to be. This is a matter of opinion :-) My goal is to have the code all NFS mounted, but at the moment our internal rollout process is localized. What's happening is the clamav installation (make install) creates a file *.tmp and removes it. This is why the process failed because I mount the directory read-only on most of the systems to prevent corruption. This is easily resolved by simply using another NFS mount from where I keep distribution src. For ClamAV, the installation will fail because the NFS mount itself is read-only (ro): As Mr. Swiger said, that's expected. I know that. I just asked if there was a way around it, and I see my solution will work (separate mount). ... I wonder if there's a clever way around this. I really don't want to go through and change the mounts to read-write -- they are read-only for a reason -- or copy the code over and install each individually. As I said, I think you're making this harder than it needs to be. You do know that after "make install" you can delete the entire source tree if you don't want to keep it? What's wrong with a small shell script? I think you misunderstand. I'm keeping the source tree -- one build for 32-bit, the other for 64-bit. It would otherwise make no sense to bring the code to each system and build repeatedly :-) ClamAV has very little overhead that I can tell, but what I'm concerned about with NFS is if these systems utilize an NFS mount, then the daily signature updates will need to be moved off; at the moment they are defaulting to: /usr/local/share/clamav /usr/local/share/clamav/mirrors.dat /usr/local/share/clamav/bytecode.cld /usr/local/share/clamav/daily.cld /usr/local/share/clamav/main.cld I can set this in the freshclam.conf file to /var/lib/clamav - but it's another directory to worry about locally which I can address with Puppet. Thanks. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Compiling and installing from an NFS mount
On 3/13/12 1:02 PM, Pierre Dehaen wrote: No, I just install on a few mail filtering machines, all Solaris... and the script is not automated: it asks for confirmation before doing each step and it shows output of commands, so you can stop the script, verify, fix, etc, and restart, skip some steps already done, and complete the update. And ss this is something I have to do every few months only, it helps to remember the exact procedure. Build on one, distribute to others can be risky if they are not at the same revision of the packages. Pierre On 13 Mar 2012 at 12:08, Shawn Bakhtiar wrote: As in administrator I would be very afraid to automate the installation or updating of any software. Are you doing many machines? If so, and they all use the same OS, why not build on one, and just distribute the build to all the others? Just sharing :) In our case, it's all the same revision/OS (RHEL 5.x) -- we have both 32- and 64-bit to contend with, therefore 2 separate builds and NFS exports. The ideal case being to import that directory tree and use that in production instead of having to roll out to each system (we do perl and other finicky builds). ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Compiling and installing from an NFS mount
On 3/14/12 7:43 AM, G.W. Haywood wrote: Hello again, On Wed, 14 Mar 2012, Forrest Aldrich wrote: What's happening is the clamav installation (make install) creates a file *.tmp and removes it. This is why the process failed because I mount the directory read-only on most of the systems to prevent corruption. This is easily resolved by simply using another NFS mount from where I keep distribution src. ... I think you misunderstand. I'm keeping the source tree ... No, I understand that you're keeping the source tree, I just don't understand why you are keeping it if you're so worried that it might become corrupted. Why not just delete it when the build is finished? Then it's most unlikely to get corrupted. :) LOL no, I'm concerned about /usr/local becoming corrupted - the binary NFS mount that we want to use on our production systems. The problem I ran into is doing a "make install" from a read-only NFS mount broke the installation as it needs to create (and remove) a *.tmp file. I had built it from another system onto that export mount. There you go making life difficult for yourself again. Why not set up your own ClamAV database mirror? I'm not sure how to do this; however, we have only about 4 or 5 machines that poll for virus updates. And the mirror would be private (not publicly accessible). In our case, it's all the same revision/OS (RHEL 5.x) -- we have both 32- and 64-bit to contend with, therefore 2 separate builds ... I understand that. What I don't understand is why you don't just build your own RPM and have your mail filtering machines install that instead of doing weird and wonderful things with NFS. I think creating custom RPMs for this is overkill for what I need. What's this 'corruption' that you're so afraid of? If you want some files to be immutable, then on Solaris look at Corruption meaning I don't want local users (even privileged) to write to the NFS mount, we want to keep the binaries (and their configs that need to be there) in a consistent state. I don't understand that. All you're doing is building in a single point of failure. NFS sucks anyway, but when it goes down all your mail filtering will go down with it. Believe me, I understand that. What we really need (for all our video and other stuff) is a SAN. But try to convince my boss' boss about that one! ;-) I gave up. I just work with what I have :-) ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] Problem compiling 0.93.3 on Solaris x86 (64bit)
Prior to posting, I searched Google and found some reports like this - though they referred to previous installations needing to be removed (which I do not have). I'm trying to compile the latest stable release on Solaris 10 x86, in 64bit -- though compiling it standard with regular GCC still gets the same error: /usr/sfw/bin/gcc -shared -Wl,-h -Wl,libclamunrar.so.4 -o .libs/libclamunrar.so.4.0.4 .libs/unrar15.o .libs/unrar.o .libs/unrar20.o .libs/unrarppm.o .libs/unrarvm.o .libs/unrarcmd.o .libs/unrarfilter.o .libs/unrarhlp.o -lz -lnsl -lsocket -lc -m64 -Wl,-M -Wl,../libclamunrar/libclamunrar.map (cd .libs && rm -f libclamunrar.so.4 && ln -s libclamunrar.so.4.0.4 libclamunrar.so.4) (cd .libs && rm -f libclamunrar.so && ln -s libclamunrar.so.4.0.4 libclamunrar.so) false cru .libs/libclamunrar.a unrar15.o unrar.o unrar20.o unrarppm.o unrarvm.o unrarcmd.o unrarfilter.o unrarhlp.o make[2]: *** [libclamunrar.la] Error 1 make[2]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3/libclamunrar' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3' make: *** [all] Error 2 It's difficult to tell what the actual problem is from this message. I'd like to compile it in 64bit mode, if possible - but I'll accept just getting it to work for now. Solaris' SFW distribution does not contain libgmp, so that functionality isn't enabled. I did install libgmp.a under /usr/local/lib (from Sunfreeware) but the compile doesn't accept it. Any pointers would be appreciated. Thanks. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Problem compiling 0.93.3 on Solaris x86 (64bit)
Török Edwin wrote: > On 2008-07-24 20:20, Forrest Aldrich wrote: > >> Prior to posting, I searched Google and found some reports like this - >> though they referred to previous installations needing to be removed >> (which I do not have). >> >> I'm trying to compile the latest stable release on Solaris 10 x86, in >> 64bit -- though compiling it standard with regular GCC still gets the >> same error: >> >> /usr/sfw/bin/gcc -shared -Wl,-h -Wl,libclamunrar.so.4 -o >> .libs/libclamunrar.so.4.0.4 .libs/unrar15.o .libs/unrar.o >> .libs/unrar20.o .libs/unrarppm.o .libs/unrarvm.o .libs/unrarcmd.o >> .libs/unrarfilter.o .libs/unrarhlp.o -lz -lnsl -lsocket -lc -m64 >> -Wl,-M -Wl,../libclamunrar/libclamunrar.map >> (cd .libs && rm -f libclamunrar.so.4 && ln -s libclamunrar.so.4.0.4 >> libclamunrar.so.4) >> (cd .libs && rm -f libclamunrar.so && ln -s libclamunrar.so.4.0.4 >> libclamunrar.so) >> false cru .libs/libclamunrar.a unrar15.o unrar.o unrar20.o unrarppm.o >> unrarvm.o unrarcmd.o unrarfilter.o unrarhlp.o >> >> > > It is supposed to call 'ar' here, is it in your path? > I remember having to edit my $PATH to include all the stuff in > /usr/xpg4/bin, and some other Solaris specific directories. > > Best regards, > --Edwin Thanks, Edwin. I'm a little new to Solairs, so this is very helpful. I managed to get past that and now I've a different sort of error: mkdir .libs /usr/sfw/bin/gcc -m64 -o .libs/clamscan output.o getopt.o cfgparser.o misc.o options.o clamscan.o others.o manager.o treewalk.o ../libclamav/.libs/libclamav.so /usr/local/src/clamav/clamav-0.93.3/libclamunrar_iface/.libs/libclamunrar_iface.so /usr/local/src/clamav/clamav-0.93.3/libclamunrar/.libs/libclamunrar.so -L/usr/local/lib -lbz2 -lz -lnsl -lsocket -lpthread -R/usr/local/lib ld: warning: file /usr/local/lib/libbz2.a(bzlib.o): wrong ELF class: ELFCLASS32 Undefined first referenced symbol in file BZ2_bzDecompress../libclamav/.libs/libclamav.so BZ2_bzRead ../libclamav/.libs/libclamav.so BZ2_bzDecompressEnd ../libclamav/.libs/libclamav.so BZ2_bzReadOpen ../libclamav/.libs/libclamav.so BZ2_bzDecompressInit../libclamav/.libs/libclamav.so BZ2_bzReadClose ../libclamav/.libs/libclamav.so ld: fatal: Symbol referencing errors. No output written to .libs/clamscan collect2: ld returned 1 exit status gmake[2]: *** [clamscan] Error 1 gmake[2]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3/clamscan' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3' gmake: *** [all] Error 2 I think this is because I'm trying to compile in 64bit mode, so I may have to give that up... Feedback welcomed. Thanks, Forrest ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Problem compiling 0.93.3 on Solaris x86 (64bit)
Török Edwin wrote: > On 2008-07-24 20:40, Forrest Aldrich wrote: > >> Török Edwin wrote: >> >> >>> On 2008-07-24 20:20, Forrest Aldrich wrote: >>> >>> >>> >>>> Prior to posting, I searched Google and found some reports like this - >>>> though they referred to previous installations needing to be removed >>>> (which I do not have). >>>> >>>> I'm trying to compile the latest stable release on Solaris 10 x86, in >>>> 64bit -- though compiling it standard with regular GCC still gets the >>>> same error: >>>> >>>> /usr/sfw/bin/gcc -shared -Wl,-h -Wl,libclamunrar.so.4 -o >>>> .libs/libclamunrar.so.4.0.4 .libs/unrar15.o .libs/unrar.o >>>> .libs/unrar20.o .libs/unrarppm.o .libs/unrarvm.o .libs/unrarcmd.o >>>> .libs/unrarfilter.o .libs/unrarhlp.o -lz -lnsl -lsocket -lc -m64 >>>> -Wl,-M -Wl,../libclamunrar/libclamunrar.map >>>> (cd .libs && rm -f libclamunrar.so.4 && ln -s libclamunrar.so.4.0.4 >>>> libclamunrar.so.4) >>>> (cd .libs && rm -f libclamunrar.so && ln -s libclamunrar.so.4.0.4 >>>> libclamunrar.so) >>>> false cru .libs/libclamunrar.a unrar15.o unrar.o unrar20.o unrarppm.o >>>> unrarvm.o unrarcmd.o unrarfilter.o unrarhlp.o >>>> >>>> >>>> >>>> >>> It is supposed to call 'ar' here, is it in your path? >>> I remember having to edit my $PATH to include all the stuff in >>> /usr/xpg4/bin, and some other Solaris specific directories. >>> >>> Best regards, >>> --Edwin >>> >>> >> Thanks, Edwin. I'm a little new to Solairs, so this is very helpful. >> >> I managed to get past that and now I've a different sort of error: >> >> mkdir .libs >> /usr/sfw/bin/gcc -m64 -o .libs/clamscan output.o getopt.o cfgparser.o >> misc.o options.o clamscan.o others.o manager.o treewalk.o >> ../libclamav/.libs/libclamav.so >> /usr/local/src/clamav/clamav-0.93.3/libclamunrar_iface/.libs/libclamunrar_iface.so >> >> /usr/local/src/clamav/clamav-0.93.3/libclamunrar/.libs/libclamunrar.so >> -L/usr/local/lib -lbz2 -lz -lnsl -lsocket -lpthread -R/usr/local/lib >> ld: warning: file /usr/local/lib/libbz2.a(bzlib.o): wrong ELF class: >> ELFCLASS32 >> Undefined first referenced >> symbol in file >> BZ2_bzDecompress../libclamav/.libs/libclamav.so >> BZ2_bzRead ../libclamav/.libs/libclamav.so >> BZ2_bzDecompressEnd ../libclamav/.libs/libclamav.so >> BZ2_bzReadOpen ../libclamav/.libs/libclamav.so >> BZ2_bzDecompressInit../libclamav/.libs/libclamav.so >> BZ2_bzReadClose ../libclamav/.libs/libclamav.so >> ld: fatal: Symbol referencing errors. No output written to .libs/clamscan >> collect2: ld returned 1 exit status >> gmake[2]: *** [clamscan] Error 1 >> gmake[2]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3/clamscan' >> gmake[1]: *** [all-recursive] Error 1 >> gmake[1]: Leaving directory `/usr/local/src/clamav/clamav-0.93.3' >> gmake: *** [all] Error 2 >> >> I think this is because I'm trying to compile in 64bit mode, so I may >> have to give that up... >> >> Feedback welcomed. >> >> > > Hmm, I thought configure was already catching this kind of bzip2 problems. > If you do have a 64-bit bzip2, try ./configure > --with-libbz2-prefix=, > for example: ./configure --with-libbz2-prefix= /usr/local/lib64 > > If you don't have 64-bit bzip2, you can either download&build it, and > install it alongside clamav, > or use ./configure --disable-bzip2 > > Best regards, > --Edwin > > /usr/sfw doesn't have bzip2 -- /usr/bin/bzip2 is a 32 bit application - so I would have to alter my PATH and then possibly install a -m64 compiled (via SUNWspro) version under /usr/sfw. Odd that the binaries for the system wouldn't at least be 64bit. Unless there is some other clever way. Thanks. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] Odd error
I have ClamAV 0.80 (via FreeBSD ports) installed. I just sent someone a file.tar.gz that had some patches included (along with *.orig files). I saw this in the logs: Oct 25 00:51:26 forrie MailScanner[4303]: ProcessClamAVOutput: unrecognised line "webuserprefs-0.5/ChangeLog". Please contact the authors! Oct 25 00:51:26 forrie MailScanner[4303]: webuserprefs-0.5/ChangeLog.orig Oct 25 00:51:26 forrie MailScanner[4303]: ProcessClamAVOutput: unrecognised line "webuserprefs-0.5/ChangeLog.orig". Please contact the authors! Oct 25 00:51:26 forrie MailScanner[4303]: webuserprefs-0.5/webuserprefs-0.5/ Oct 25 00:51:26 forrie MailScanner[4303]: ProcessClamAVOutput: unrecognised line "webuserprefs-0.5/webuserprefs-0.5/". Please contact the authors! Oct 25 00:51:26 forrie MailScanner[4303]: webuserprefs-0.5/webuserprefs-0.5/ChangeLog Oct 25 00:51:26 forrie MailScanner[4303]: ProcessClamAVOutput: unrecognised line "webuserprefs-0.5/webuserprefs-0.5/ChangeLog". Please contact the authors! Oct 25 00:51:26 forrie MailScanner[4303]: webuserprefs-0.5/webuserprefs-0.5/ChangeLog.orig Oct 25 00:51:26 forrie MailScanner[4303]: ProcessClamAVOutput: unrecognised line "webuserprefs-0.5/webuserprefs-0.5/ChangeLog.orig". Please contact the authors! And so I figured I'd send this here to see what the problem might be. Thanks. ___ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Re: [clamav-users] Compiling clamav on FreeBSD
It does. ls, dir, whatever so something isn't working. I can't compile the clamav-milter on this system - the make process doesn't compile that or clamd, as specified in my previous post. I'd like to understand (and possibly fix) the problem. Forrest At 01:29 AM 6/17/2003, Nigel Horne wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > ftp> ls * > ftp: connect: Connection refused I'm not sure what "ls *" does. I thought ls doesn't take an argument in ftp speak. - -Nigel Horne - -- Nigel Horne. Arranger, Composer, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 [EMAIL PROTECTED] http://www.bandsman.co.uk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7qdVhTUd3VwpF6IRAutoAKCokQ8Tc0oPbIsa0pkUoWMLHJZ2/ACdExvj nQPEUFfEO0Ro9z24gW4DkfE= =VOIL -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[clamav-users] What happened with elecktrapro.com ?
What happened with clamav.elektrapro.com that caused the extended downtime? I didn't see anything posted to that effect. And what about hosting this project on sourceforge? F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav-milter compiling on FreeBSD?
(hmm, looks like clamav.elektrapro.com has been down for a while... ?) I installed GCC33, with no problems. When I go to compile from a recent snapshot release, I use the flags: ./configure --prefix=/usr/local --disable-pthreads --enable-milter --with-gcc=/usr/local/bin/gcc33 and it does not build clamav-milter. The directory is still: .deps MakefileMakefile.in clamav-milter.sh INSTALL Makefile.am clamav-milter.c clamd.sh I used --disable-pthreads, since the FreeBSD port also calls for this - I don't know why, or whether pthreads are unstable on this platform. Doing a make in that directory does nothing, and there are some things in the Makefile that are commented out from the configure process, so I'm not sure what's happening. I also noted that nothing was made in the clamd directory, either. Trying to do a "gmake" in any of these generates errors, due to other things not being present. This is on FreeBSD-4.8, GNU Make 3.80, and GCC 3.3, using BASH 2.05b. Forrest - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] Compiling clamav on FreeBSD
I can get to the site, but (even in PASV) can't see the directory. Anyhow, I would like to compile this from source... and would like to understand why I'm having these compile problems with the latest snapshot. Do you have a CVS server somewhere? At 06:03 AM 6/13/2003, Nigel Horne wrote: You can ftp the binary of clamav-milter for FreeBSD4.8 from 212.159.106.41. -Nigel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav-milter compiling on FreeBSD?
Thanks Nigel, sorry for the oversight. Why, may I ask, does this depend upon GCC3? Thanks, Forrest At 02:05 AM 6/6/2003, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 Jun 2003 3:15 am, Forrest Aldrich wrote: > I can't seem to get clamav-milter to compile on FreeBSD_4.8, and I wonder > if anyone has accomplished this. You must use GCC3 which comes with the ports. See .../clamav-milter/INSTALL - -Nigel - -- Nigel Horne. Arranger, Composer, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 [EMAIL PROTECTED] http://www.bandsman.co.uk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+4C8UhTUd3VwpF6IRAoZ8AJ9cqtGkLO6NPKS8oh3c2bkiQWuHzACggBbz aGYh/+r998dWCQ1/rxcph5M= =z3b5 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav 0.60 bugs / RPMs hosting proposal
I would think this (and other related issues, like clamav.elektrapro.com going offline frequently) would be so much easier if ClamAV were maintained on SourceForge. At 06:03 AM 6/24/2003, Lionel Bouton wrote: Krištof Petr wrote: Lionel Bouton wrote: [..] BTW, are there people interested by RedHat RPMs around here ? I'm in the process of generating them. I build them on RedHat 8.0 but at least the src.rpm should be usable anywhere (in the contrary I'll consider it a bug). I plan to host them on our web site. Im using rpms avalaible from ftp://crash.fce.vutbr.cz/pub/linux/clamav/ Petr I see, but I've a different approach for a few things : - No fixed clamav uid/gid. They can clash with another user and prevent clamav from installing. (Is there a benefit for using a particular uid/gid couple ?). - clamav.conf modifications are provided as a patch to ease upgrade to newer clamav versions. - The binary RPM is splitted between libclamav, clamscan, clamd and clamav-db. - We don't have clamav-milter (we use amavis and postfix). I think people might benefit from several RPM based distribution as they will be more tuned to their needs. Yours is clearly sendmail oriented for example. Ours is more independant and needs more glue to make it work. Tomasz, would it be possible to set up a few links on clamav.elektrapro.com to packager's work ? I would have loved to be directed to Petr's work in the first place. LB. -- Lionel Bouton - inet6 - o Siege social: 51, rue de Verdun - 92158 Suresnes / _ __ _ Acces Bureaux: 33 rue Benoit Malon - 92150 Suresnes / /\ /_ / /_ France \/ \/_ / /_/ Tel. +33 (0) 1 41 44 85 36 Inetsys S.A.Fax +33 (0) 1 46 97 20 10 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[clamav-users] clamav-milter compiling on FreeBSD?
I can't seem to get clamav-milter to compile on FreeBSD_4.8, and I wonder if anyone has accomplished this. This is from the latest CVS snapshot of ClamAV. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] Compiling clamav on FreeBSD
Rob, were you able to get clamav-milter running on FreeBSD-4.8? I cannot. If so, could you share your config args, etc. Thanks, Forrest At 01:01 PM 6/11/2003, Rob wrote: Rob wrote: Hi clamav compiles and runs on my FBSD-4.8 system, but I get warnings at the end of compilation: /usr/lib/libc.so: WARNING! setkey(3) not present in the system! /usr/lib/libc.so: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: this program uses f_prealloc(), which is not recommended. /usr/lib/libc.so: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so: warning: tempnam() possibly used unsafely; consider using mkstemp() Can I safely ignore this or is there a way to point clamav to the right library ? Rob Evers Sorry I wan't clear in my post I'm compiling clamav-20030605.tar.gz. Rob -- f u cn rd ths u r usng unx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] Compiling clamav on FreeBSD
At 03:47 AM 6/14/2003, Nigel Horne wrote: On Friday 13 June 2003 21:53, Forrest Aldrich wrote: > I can get to the site, but (even in PASV) can't see the directory. When you see "can't see the directory" what error message do you see? What directory are you trying to access? What command are you using to try to see it? Please cut 'n' paste a screen dump so that I can see what's going on. [ ... ] Here's the log: # ftp 212.159.106.41 Connected to 212.159.106.41. 220 bandsman.co.uk FTP server (Version wu-2.6.2-8) ready. Name (212.159.106.41:forrie): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to I. ftp> prom Interactive mode off. ftp> dir ftp: connect: Connection refused ftp> ls * ftp: connect: Connection refused ftp> cd / 250 CWD command successful. ftp> cd pub 250 CWD command successful. ftp> dir ftp: connect: Connection refused ftp> quit 221-You have transferred 0 bytes in 0 files. 221-Total traffic for this session was 560 bytes in 0 transfers. 221-Thank you for using the FTP service on bandsman.co.uk. 221 Goodbye. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav-milter compiling on FreeBSD?
Also, I see this in the configure output: checking libmilter/mfapi.h usability... yes checking libmilter/mfapi.h presence... yes checking for libmilter/mfapi.h... yes I re-ran everything, from a fresh untar of the latest snapshot, and still... nothing is being made in the clamd or lib-milter directories, despite my configure args: ./configure --prefix=/usr/local --disable-pthreads --enable-milter --with-gcc=/usr/local/bin/gcc33 Forrest - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[clamav-users] disinfect?
Someone mentioned on MailScanner that ClamAV doesn't actually disinfect, just notifies. Are there plans for a disinfection ability. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav update problem
At 03:48 AM 6/9/2003, Ahmad Masood Shah wrote: There was problem in clamv system. Now they have recoverd ... updating is working now.. [ ... ] Glad the problem is fixed. I certainly tried to find out what had happened, but didn't get any information. I'd like to suggest that ClamAV be moved to SourceForge.net. This would resolve these types of outage problems, and would place less reliability upon one or two web sites for making the code and snapshots available. Consider? Forrest - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [clamav-users] clamav-milter compiling on FreeBSD?
Yes, libmilter files are properly installed, via the FreeBSD "sendmail-old" port. They are : /usr/local/lib/libmilter.a /usr/local/include/libmilter: mfapi.h At 01:16 PM 6/9/2003, you wrote: > (hmm, looks like clamav.elektrapro.com has been down for a while... ?) > > I installed GCC33, with no problems. > > When I go to compile from a recent snapshot release, I use the flags: > > ./configure --prefix=/usr/local --disable-pthreads --enable-milter > --with-gcc=/usr/local/bin/gcc33 > > and it does not build clamav-milter. The directory is still: > > .deps MakefileMakefile.in > clamav-milter.sh > INSTALL Makefile.am clamav-milter.c > clamd.sh Do you have libmilter development files properly installed ? Best regards, Tomasz Kojm -- oo. [EMAIL PROTECTED] (\/)\. http://www.konarski.edu.pl/~zolw \..._ I nie zapomnij kliknac w brzuszek... //\ /\\ <- C. Amboinensiswww.pajacyk.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Clamav-users] False positive for Cake.A virus?
I have a file that was detected to have the Cake.A virus; however, my other scanners (Norton, Ravav, F-Prot, Nod32) do not concur. Anyone see this type of false positive. Forrest --- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 ___ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
