Mailing List Archive

1 2  View All
Re: [clamav-users] can't cmake 1.0.4rc [ In reply to ]
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
Re: [clamav-users] can't cmake 1.0.4rc [ In reply to ]
On Friday 30 July 2021 03:32:44 Arjen de Korte via clamav-users wrote:

> 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.
>
I see by synaptic, that both python-test and python3-test are available.
Which is preferred? I'd assume python3-test in order to future proof, but
assumptions are where we've gone aglay too many times already.

Thanks Arjen.

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

_______________________________________________

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
Re: [clamav-users] can't cmake 1.0.4rc [ In reply to ]
On Fri, 30 Jul 2021, Gene Heskett via clamav-users wrote:

> I see by synaptic, that both python-test and python3-test are available.
> Which is preferred? I'd assume python3-test in order to future proof, but
> assumptions are where we've gone aglay too many times already.

My experience on fast-track Ubuntu (not specifically with clamav)
is that you need the package which matches the python you wish
to use to run the tests.

--
Andrew C. Aitchison Kendal, UK
andrew@aitchison.me.uk

_______________________________________________

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
Re: [clamav-users] can't cmake 1.0.4rc [ In reply to ]
On Thu, 29 Jul 2021, Gene Heskett via clamav-users wrote:

> 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.

Now that we have the announcement of ClamAV 0.103 LTS, supported until
August?September 2023, I think Stretch users should stay with ClamAV 0.103
rather than shifting to 104 and CMake.

--
Andrew C. Aitchison Kendal, UK
andrew@aitchison.me.uk

_______________________________________________

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

1 2  View All