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.
This is a friendly reminder, and ponce: please feel free to remove if inappropriate or better suited to another thread.
claws-mail users: you should rebuild.
I began to have all sorts of strange crashes on the software. I was able to pinpoint those traces to the Perl plugin. Was about to file a serious bug report upstream when it dawned to me that Pat just recently updated perl and so it should be recompiled.
I rebuilt the package and all problems went away. So, I advise to rebuild, especially to those who have the Perl plugin loaded. After rebuilding claws was as stable as ever.
Last edited by sombragris; 05-26-2021 at 09:22 AM.
that happens because you haven't log out and log in again from your root session after having installed google-go-lang.
Thanks for the quick reply. But it still happens even after rebooting the machine. Could this be caused by running multilib? You mentioned that this could lead to problems..
Thanks for the quick reply. But it still happens even after rebooting the machine. Could this be caused by running multilib? You mentioned that this could lead to problems..
no, the error happens because you are still using gcc's go and not the go compiler from google-go-lang, the error is clear
Quote:
go build -trimpath "-mod=vendor" "-buildmode=pie" -tags "seccomp" -ldflags "-X main.gitCommit=12644e614e25b05da6fd08a38ffa0cfe1903fdec -X main.version=1.0.0-rc93 " -o runc .
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags
so check that you have installed correctly google-go-lang and the output (from the root shell from which you are trying to build runc) of
file: config/paths-slackware.conf
apache_error_log = /var/log/httpd/*error.log
to
apache_error_log = /var/log/httpd/*error_log
AND
apache_access_log = /var/log/httpd/*access.log
to
apache_access_log = /var/log/httpd/*access_log
as apache slackware 14.2-current log files now points to those locations.
I should had sent a patch file in this case but I do not have enough experience handling original/modified (diff -u ) to generate the patch correctly to apply. Please let me know how to do it so I can make it next time.
Finally, there is a new stable version: fail2ban ver. 0.11.2 (2020/11/23).
I sent an email with this comments to fail2ban maintainer Nishant Limbachia. It seems there are problems with his email.
file: config/paths-slackware.conf
apache_error_log = /var/log/httpd/*error.log
to
apache_error_log = /var/log/httpd/*error_log
AND
apache_access_log = /var/log/httpd/*access.log
to
apache_access_log = /var/log/httpd/*access_log
as apache slackware 14.2-current log files now points to those locations.
I should had sent a patch file in this case but I do not have enough experience handling original/modified (diff -u ) to generate the patch correctly to apply. Please let me know how to do it so I can make it next time.
Finally, there is a new stable version: fail2ban ver. 0.11.2 (2020/11/23).
I sent an email with this comments to fail2ban maintainer Nishant Limbachia. It seems there are problems with his email.
Thanks for your support.
Francisco.
Hi Francisco,
you can find Nishant's new address in the phpmyadmin script that he maintains: please report him also about his old email if it isn't working.
[641/925] Compiling C object ext/hls/libgsthls.so.p/gsthlssink.c.o
[642/925] Compiling C object ext/fluidsynth/libgstfluidsynthmidi.so.p/gstfluiddec.c.o
[643/925] Compiling C object ext/hls/libgsthls.so.p/gsthlssink2.c.o
[644/925] Compiling C object ext/hls/libgsthls.so.p/gsthlsdemux.c.o
../ext/hls/gsthlsdemux.c: In function ‘gst_hls_demux_update_fragment_info’:
../ext/hls/gsthlsdemux.c:1127:3: warning: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Wdeprecated-declarations]
1127 | hlsdemux_stream->current_iv = g_memdup (file->iv, sizeof (file->iv));
| ^~~~~~~~~~~~~~~
In file included from /usr/include/glib-2.0/glib.h:82,
from /usr/include/gstreamer-1.0/gst/gst.h:27,
from /usr/include/gstreamer-1.0/gst/base/gsttypefindhelper.h:27,
from ../ext/hls/gsthlsdemux.c:45:
/usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
257 | gpointer g_memdup (gconstpointer mem,
| ^~~~~~~~
[645/925] Compiling C object ext/hls/libgsthls.so.p/m3u8.c.o
ninja: build stopped: subcommand failed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
