SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not so much building, but running: since the pam inclusion of yesterday:
Code:
bash-5.0$ /etc/rc.d/rc.clamav start
Starting clamd daemon: /usr/sbin/clamd chown: changing ownership of '/var/run/clamav/': Operation not permitted
chmod: changing permissions of '/var/run/clamav/': Operation not permitted
LibClamAV Warning: Detected duplicate databases /var/lib/clamav/main.cvd and /var/lib/clamav/main.cld, please manually remove one of them
One of the first lines of /etc/rc.d/rc.clamav start is a chown...
freshclam works
EDIT: latest clamav-0.102.3
I don't have those errors...
could it be because you are starting the daemon as user (I'm judging by the prompt you pasted)?
One of the ./configure options in cinelerra.SlackBuild is "--with-plugindir."
Should not that be "--with-plugin-dir"?
yes, thanks for pointing this out: it seems like in the git version of cinelerra-gg, to which I have to switch because the old one won't build on current, this option has silently changed.
mpich.SlackBuild failed during configure with this error message: "The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types." I traced the problem to a legacy configure test. The package builds with FFLAGS="-fallow-argument-mismatch", but "Using this option is strongly discouraged." --https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html
This issue is discussed here: https://github.com/pmodels/mpich/issues/4300
mpich.SlackBuild failed during configure with this error message: "The Fortran compiler gfortran will not compile files that call the same routine with arguments of different types." I traced the problem to a legacy configure test. The package builds with FFLAGS="-fallow-argument-mismatch", but "Using this option is strongly discouraged." --https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html
This issue is discussed here: https://github.com/pmodels/mpich/issues/4300
as it seems to build fine here I suspect what I wrote a few posts above applies to this too
Quote:
Originally Posted by ponce
could it be you forgot to say that you are using gcc-10.x from /testing?
[...]
I started to push some patches to the repository for gcc-10.x but I will stop until it will get out of /testing and into the distribution, so please don't report other building issues in this topic if you have it installed.
as it seems to build fine here I suspect what I wrote a few posts above applies to this too
Yes, indeed. I didn't read #2723 on the previous page. I did not realize Slackware-current was still using the March 2020 version, since gcc 10 came out over a fortnight ago. My bad. I last used fortran in the 70's, so when I saw the error message, I went to the gcc.gnu.org gfortran manual without realizing that it was version 10. I'll go away now.
Obquote: "Sorry about that!" -Maxwell Smart, Secret Agent 86.
fltk is in Slackware now, so I think it should be removed. Thanks!
it's still in /extra, but it was also with 14.2: as it's a dependency of stuff on SBo it's also there (and in this repository), like jdk (for example).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.