Here is the result of my make install:

fexter@fexter-desktop:~/clamav-0.92rc2$ make install
Making install in libclamav
make[1]: Entering directory `/home/fexter/clamav-0.92rc2/libclamav'
make[2]: Entering directory `/home/fexter/clamav-0.92rc2/libclamav'
test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib"
/bin/bash ../libtool --mode=install /usr/bin/install -c 'libclamav.la' '/usr/local/lib/libclamav.la'
/usr/bin/install -c .libs/libclamav.so.3.0.1 /usr/local/lib/libclamav.so.3.0.1
/usr/bin/install: cannot create regular file `/usr/local/lib/libclamav.so.3.0.1': Permission denied
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/home/fexter/clamav-0.92rc2/libclamav'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/fexter/clamav-0.92rc2/libclamav'
make: *** [install-recursive] Error 1

Can someone explain to me how come it doesn't work?

Greatly appreciated!

Fexter

At least here's a problem: make install (usually) copies files to directories you don't necessarily have write permissions, as a normal user, so for that reason 'make install' should be ran either as root, or with root privileges (trough sudo, for example). The dollar sign ($) above suggests that you're running 'make install' not as root, but as a regular user, and that doesn't work

EDIT: also "fexter@fexter-desktop" sounds like you're issuing the command as user 'fexter', whose rights aren't as high as 'root's.

Configuration step (./configure) and compiling step (make) can and should be done as a regular user, since they don't usually deal with things that require root privileges. But do the last step with root privileges.

Ok great that worked just fine!! But now I do a sudo freshclam but it tells me to go edit the freshclam.conf file. I have no clue what I need to do. Is it just removing the # signs?

Well, the file freshclam.conf (in /etc/ probably, but I'm not sure) is the configuration for the program. By default, if I'm right, there is a variable set that prevents the normal startup of the program and causes it to tell you to edit the file -- this is because the program maker wants that you don't just blindly run it, but read the configuration file trough and modify the options to suit your needs.

So, what you do, is open the file as root (using sudo) with your favourite text editor. Go trough the options; don't remove every comment mark (#) because that either makes the file unusable (wrong lines uncommented, like real comments), or causes things to be un/set that you really don't want to. Instead read the lines trough, and decide which options you want to be set on or off (or to some value), and which ones you want to have at their default values. You don't need to edit lines you think are ok for you, but you can and should edit those values you think are important.

When you've reviewed the configuration options (most of them may well be ok for you), then find the line that says something like "remove this line to allow the program run", and comment it - add # in front of the line (it could also be made so that you need to uncomment something, but you'll see when you read it).

That step is taken in some other programs as well, to make sure the user who installs the program does read the configuration trough and doesn't just jump into using it.

Thanks a whole bunch b0uncer! Thats what I thought but I wasn't too sure!

Dude you rock!!

No problem - if any further questions happen to come to your mind, feel free to ask You can also IM me if you like, and if I happen to be online then.

IM? within this forum??? Im so new its nuts!!!

No, not in this forum (that would be awesome, depending on the users themselves), but if you happen to have one of those IM apps installed (Pidgin, Kopete etc..for ICQ for example), you are able to throw me a message.

Oh ok thats what I thought!