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.
The maintainer ought to be familiar with programming, libraries, etc, on everyday basis ... In my case that would be difficult.
I'm certainly no programmer, yet I maintain over 30 scripts on SBo. I know enough to write a SlackBuild, but if a program needs patching, I have to look somewhere else for someone else's work.
libffado , not build...this is the last messages from console.
Quote:
In file included from src/libutil/IpcRingBuffer.h:37:0,
from src/libutil/IpcRingBuffer.cpp:24:
src/libutil/PosixMessageQueue.h:117:38: error: ‘sigval_t’ no se ha declarado
static void notifyCallbackStatic(sigval_t t) {
^~~~~~~~
src/libutil/PosixMessageQueue.h: En la función miembro static ‘static void Util::PosixMessageQueue::notifyCallbackStatic(int)’:
src/libutil/PosixMessageQueue.h:119:50: error: solicitud por el miembro ‘sival_ptr’ en ‘t’, el cual es del tipo ‘int’ que no es clase
obj = static_cast<PosixMessageQueue *>(t.sival_ptr);
^~~~~~~~~
scons: *** [src/libutil/IpcRingBuffer.os] Error 1
scons: building terminated because of errors.
I build 2.4.1 version without problem.
Last edited by USUARIONUEVO; 03-23-2018 at 07:41 PM.
libffado , not build...this is the last messages from console.
Code:
In file included from src/libutil/IpcRingBuffer.h:37:0,
from src/libutil/IpcRingBuffer.cpp:24:
src/libutil/PosixMessageQueue.h:117:38: error: ‘sigval_t’ no se ha declarado
static void notifyCallbackStatic(sigval_t t) {
^~~~~~~~
src/libutil/PosixMessageQueue.h: En la función miembro static ‘static void Util::PosixMessageQueue::notifyCallbackStatic(int)’:
src/libutil/PosixMessageQueue.h:119:50: error: solicitud por el miembro ‘sival_ptr’ en ‘t’, el cual es del tipo ‘int’ que no es clase
obj = static_cast<PosixMessageQueue *>(t.sival_ptr);
^~~~~~~~~
scons: *** [src/libutil/IpcRingBuffer.os] Error 1
scons: building terminated because of errors.
Halberd fails to build, due to a patch for the documentation make file, that points to the wrong latex (from 14.2). This is due to the change to texlive that was added to current a while back. See attached patch.
Halberd fails to build, due to a patch for the documentation make file, that points to the wrong latex (from 14.2). This is due to the change to texlive that was added to current a while back. See attached patch.
Lutris builds successfully on -current after removing pygobject3-python3 and dbus-python3 from the Lutris REQUIRES, and after removing python3 from the python3-PyYAML REQUIRES. All three dependencies already exist in -current. See attached.
Hi , i have issues with gst-plugins-bad , it builds only if no wayland package is present on system (wayland and wayland-protocols)
Error says ever same arround gtk , cause gtk is not build with wayland
Quote:
make -C audiomixmatrix
make[4]: se entra en el directorio '/tmp/SBo/gst-plugins-bad-1.14.0/tests/examples/audiomixmatrix'
CC test_audiomixmatrix-test-audiomixmatrix.o
CCLD test-audiomixmatrix
main.c:28:2: error: #error "Wayland is not supported in GTK+"
#error "Wayland is not supported in GTK+"
when no wayland on system , plugins-bad builds , but after reboot , some apps have issues cause , mismatch versions.
1 - please update to 1.14.0 plugins components
2 - to prevent wayland errors , the easy way is add
Quote:
--disable-examples
cause try to build examples with gtk and wayland support , then get an build error.
--------------
short story , if no wayland , then builds , but apps issues , (go with 1.14.0 are ok there)
to prevent wayland on some systems fails to build , add --disable-examples to the build script.
Lutris builds successfully on -current after removing pygobject3-python3 and dbus-python3 from the Lutris REQUIRES, and after removing python3 from the python3-PyYAML REQUIRES. All three dependencies already exist in -current. See attached.
Ponce's repo doesn't track dependency changes because of the already giant burden of maintaining so many branches and those slackbuilds are only required for 14.2. If you're using current then its your responsibility to check the dependencies yourself.
While building perl-http-server-simple, I get the following error:
Code:
Can't locate inc/Module/Install.pm in @INC (you may need to install the inc::Module::Install module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at Makefile.PL line 1.
BEGIN failed--compilation aborted at Makefile.PL line 1.
Setting the following variable allows it to build successfully.
Ponce's repo doesn't track dependency changes because of the already giant burden of maintaining so many branches and those slackbuilds are only required for 14.2. If you're using current then its your responsibility to check the dependencies yourself.
Yeah I know. I am going through the SlackBuilds I maintain and making sure they all build on -current. Should I not report dependencies that are missing or unneeded?
Should I not report dependencies that are missing or unneeded?
it's ok to report missing dependencies, but dependencies added to slackware current will be removed only when we will be close to the 15 release, to avoid pain during the various rebasing of the git branches, so you can avoid reporting those.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.