Citeren Gene Heskett via clamav-users <clamav-users@lists.clamav.net>:
> Well, I've screwed around with this for 3 days now, that's long enough.
>
> First gotcha for debian people is cmake is not installed, and when
> installed, it is NOT installed in a directory accessible to the user
> with a default $PATH, so the first thing I have to do is give it the
> full path to where its installed. And apparently there are no man pages,
> strike two.
>
> Second gotcha is cmake needs about 7 or so more bits installed that in 23
> years of exclusively linux in this house I have never needed before just
> to get thru the configure and build something. Strikes 3 thru 9 or 10
>
> Third gotcha is that the default build puts it in /usr/local, a normal
> occurrence for stuff built from tarballs, without building new stuff
> for /etc/init.d that tells it where to find the executables NOW.
> Depending on a 1/4 baked systemd on an older stretch install isn't doing
> one a bit of good unless perchance you are rebooting.
We can´t blame the ClamAV developers that we're cmake novices. I too
was unfamiliar with cmake, so I'm on a steep learning curve as well.
And it looks like Debian can do a better job by providing a cmake that
actually works. Nothing to blame ClamAV for.
> Please let us know when this is actually installable and working when the
> notes in INSTALL.md are followed. It is not ready for prime time now.
I beg to differ. I followed the INSTALL.md and it took me less than
two hours tweaking the options to have a similar result as with the
previous autotools. Note that I'm building in a openSUSE system, which
provides %cmake macros in a similar way as %make macros that relieves
one of the burden to figure out the distribution specific settings. I
was pleasantly surprised how smooth the transition actually went. Just
a handful of bugs, but that's what release candidates are for (to iron
them out).
> You can start by listing the dependencies AND the packages they are found
> in, in INSTALL.md so we can install them without any excitement.
The only additional package I needed was python-pytest, all other
dependencies are identical.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
> Well, I've screwed around with this for 3 days now, that's long enough.
>
> First gotcha for debian people is cmake is not installed, and when
> installed, it is NOT installed in a directory accessible to the user
> with a default $PATH, so the first thing I have to do is give it the
> full path to where its installed. And apparently there are no man pages,
> strike two.
>
> Second gotcha is cmake needs about 7 or so more bits installed that in 23
> years of exclusively linux in this house I have never needed before just
> to get thru the configure and build something. Strikes 3 thru 9 or 10
>
> Third gotcha is that the default build puts it in /usr/local, a normal
> occurrence for stuff built from tarballs, without building new stuff
> for /etc/init.d that tells it where to find the executables NOW.
> Depending on a 1/4 baked systemd on an older stretch install isn't doing
> one a bit of good unless perchance you are rebooting.
We can´t blame the ClamAV developers that we're cmake novices. I too
was unfamiliar with cmake, so I'm on a steep learning curve as well.
And it looks like Debian can do a better job by providing a cmake that
actually works. Nothing to blame ClamAV for.
> Please let us know when this is actually installable and working when the
> notes in INSTALL.md are followed. It is not ready for prime time now.
I beg to differ. I followed the INSTALL.md and it took me less than
two hours tweaking the options to have a similar result as with the
previous autotools. Note that I'm building in a openSUSE system, which
provides %cmake macros in a similar way as %make macros that relieves
one of the burden to figure out the distribution specific settings. I
was pleasantly surprised how smooth the transition actually went. Just
a handful of bugs, but that's what release candidates are for (to iron
them out).
> You can start by listing the dependencies AND the packages they are found
> in, in INSTALL.md so we can install them without any excitement.
The only additional package I needed was python-pytest, all other
dependencies are identical.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml