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 SlackBuild for strongswan (5.3.4) does not build under -current but fails with errors.
I found nothing for strongswan in Ponce's -current SlackBuilds repo.
Substituting the most recent version of strongswan (https://download.strongswan.org/strongswan-5.6.2.tar.gz)
does work with the SlackBuild after a change of the strongswan version to 5.6.2 resulting in functional package.
The SlackBuild for strongswan (5.3.4) does not build under -current but fails with errors.
I found nothing for strongswan in Ponce's -current SlackBuilds repo.
Substituting the most recent version of strongswan (https://download.strongswan.org/strongswan-5.6.2.tar.gz)
does work with the SlackBuild after a change of the strongswan version to 5.6.2 resulting in functional package.
Last time I've come here, I've been to report that VirtualBox doesn't build on -current. But this time, I am trying to rebuild all the essential packages virtualbox virtualbox-extensions-pack and virtualbox-kernel. Because I've update my Kernel version on -current.
So as virtualbox requires virtualbox-kernel, I've started to looking for updates on ponce-repository and did not find anything about it, unless the last fix which is related to virtualbox package not virtualbox-kernel.
The virtualbox-kernel SBo package make a notes about if I need to use a different kernel version just put KERNEL=4.14.24 ./virtualbox-kernel.SlackBuild, but this don't work too.
Code:
virtualbox-kernel-5.0.40/vboxnetflt/math/gcc/umoddi3.c
virtualbox-kernel-5.0.40/vboxnetflt/math/gcc/moddi3.c
virtualbox-kernel-5.0.40/vboxnetflt/SUPDrvIDC.h
*** Building 'vboxdrv' module ***
make[1]: Entering directory '/tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv'
make KBUILD_VERBOSE= SUBDIRS=/tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv SRCROOT=/tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv CONFIG_MODULE_SIG= -C /lib/modules/4.14.24/build modules
make[2]: Entering directory '/usr/src/linux-4.14.24'
CC [M] /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o
In file included from ./include/linux/atomic.h:5:0,
from ./include/linux/jump_label.h:186,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:19,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.c:32:
./arch/x86/include/asm/atomic.h: In function ‘atomic_try_cmpxchg’:
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand ‘new’
return try_cmpxchg(&v->counter, old, new);
^~~~~~
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand ‘new’
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand ‘new’
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand ‘new’
In file included from ./arch/x86/include/asm/atomic.h:276:0,
from ./include/linux/atomic.h:5,
from ./include/linux/jump_label.h:186,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:19,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.c:32:
./arch/x86/include/asm/atomic64_64.h: In function ‘atomic64_try_cmpxchg’:
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named operand ‘new’
return try_cmpxchg(&v->counter, old, new);
^~~~~~
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named operand ‘new’
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named operand ‘new’
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named operand ‘new’
make[3]: *** [scripts/Makefile.build:321: /tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[2]: *** [Makefile:1508: _module_/tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv] Error 2
make[2]: Leaving directory '/usr/src/linux-4.14.24'
make[1]: *** [Makefile:299: vboxdrv] Error 2
make[1]: Leaving directory '/tmp/SBo/virtualbox-kernel-5.0.40/vboxdrv'
make: *** [Makefile:40: all] Error 2
I've trying to trace what/where errors occours, but I don't figure out.
Hydrogen failed to build for me unless Raptor is installed. Raptor isn't listed as a dependency. I have some of the optional dependencies installed for hydrogen.
Thanks for your advice. As you said, I've tried to compile virtualbox-kernel-5.2.4 (there is virtualbox-5.2.8 but this hasn't all the components with the same version, like virtualbox-kernel), and it works! Now, I'm trying to virtualbox-5.2.4 with some changes in patches on SBo script for 5.0.40 and I take this errors
Code:
INST VBoxSharedCrOpenGL => {C}/out/linux.amd64/release/bin/VBoxSharedCrOpenGL.so
INST VirtualBox => {C}/out/linux.amd64/release/bin/VirtualBox
build debug: VBOX_WITH_NO_GCC_WARNING_POLICY is enabled
CXX VBoxFUSE - {C}/VBoxFUSE.cpp
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:112:5: error: ‘PVBOXHDD’ does not name a type; did you mean ‘PVBOXTSS’?
PVBOXHDD pDisk;
^~~~~~~~
PVBOXTSS
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘bool vboxfuseNodeDestroy(PVBOXFUSENODE, bool)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:200:29: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
if (pFlatImage->pDisk)
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:202:47: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
int rc2 = VDClose(pFlatImage->pDisk, false /* fDelete */); AssertRC(rc2);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:203:29: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
pFlatImage->pDisk = NULL;
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘void vboxfuseNodeRetain(PVBOXFUSENODE)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:268:13: warning: unused variable ‘cNewRefs’ [-Wunused-variable]
int32_t cNewRefs = ASMAtomicIncS32(&pNode->cRefs);
^~~~~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseFlatImageCreate(const char*, const char*, VBOXFUSEFLATIMAGE**)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:530:5: error: ‘PVBOXHDD’ was not declared in this scope
PVBOXHDD pDisk = NULL;
^~~~~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:530:5: note: suggested alternative: ‘PVBOXTSS’
PVBOXHDD pDisk = NULL;
^~~~~~~~
PVBOXTSS
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:531:53: error: ‘pDisk’ was not declared in this scope
rc = VDCreate(NULL /* pVDIIfsDisk */, enmType, &pDisk);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:559:28: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
pNewFlatImage->pDisk = pDisk;
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:561:73: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
pNewFlatImage->cReaders = VDIsReadOnly(pNewFlatImage->pDisk) ? INT32_MAX / 2 : 0;
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:563:70: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
pNewFlatImage->Node.cbPrimary = VDGetSize(pNewFlatImage->pDisk, 0 /* base */);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseOp_readdir(const char*, void*, fuse_fill_dir_t, off_t, fuse_file_info*)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:906:43: warning: unused parameter ‘pszPath’ [-Wunused-parameter]
static int vboxfuseOp_readdir(const char *pszPath, void *pvBuf, fuse_fill_dir_t pfnFiller,
^~~~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseOp_releasedir(const char*, fuse_file_info*)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:965:46: warning: unused parameter ‘pszPath’ [-Wunused-parameter]
static int vboxfuseOp_releasedir(const char *pszPath, struct fuse_file_info *pInfo)
^~~~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseOp_release(const char*, fuse_file_info*)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1104:43: warning: unused parameter ‘pszPath’ [-Wunused-parameter]
static int vboxfuseOp_release(const char *pszPath, struct fuse_file_info *pInfo)
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseOp_read(const char*, char*, size_t, off_t, fuse_file_info*)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1203:46: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile, pbBuf, cbBuf);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1213:50: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1223:54: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1239:54: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile, pbBuf, cbRead);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1253:54: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1162:40: warning: unused parameter ‘pszPath’ [-Wunused-parameter]
static int vboxfuseOp_read(const char *pszPath, char *pbBuf, size_t cbBuf,
^~~~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function ‘int vboxfuseOp_write(const char*, const char*, size_t, off_t, fuse_file_info*)’:
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1323:47: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDWrite(pFlatImage->pDisk, offFile, pbBuf, cbBuf);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1333:50: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1338:55: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDWrite(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1347:54: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1355:59: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDWrite(pFlatImage->pDisk, offFile & VBOXFUSE_MIN_SIZE_MASK_BLK, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1364:55: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDWrite(pFlatImage->pDisk, offFile, pbBuf, cbWrite);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1378:54: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDRead(pFlatImage->pDisk, offFile, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1382:59: error: ‘VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}’ has no member named ‘pDisk’
rc2 = VDWrite(pFlatImage->pDisk, offFile, abBlock, VBOXFUSE_MIN_SIZE);
^~~~~
/tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:1282:41: warning: unused parameter ‘pszPath’ [-Wunused-parameter]
static int vboxfuseOp_write(const char *pszPath, const char *pbBuf, size_t cbBuf,
^~~~~~~
kmk: *** [/tmp/SBo/VirtualBox-5.2.4/out/linux.amd64/release/obj/VBoxFUSE/VBoxFUSE.o] Error 1
The failing command:
@g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-va
riable -Wunused-function -Wunused-label -Wunused-parameter -Wno-overloaded-virtual -Wno-variadic-macros -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE
_VISIBILITY_DEFAULT -fvisibility-inlines-hidden -m64 -I/tmp/SBo/VirtualBox-5.2.4/out/linux.amd64/release/obj/VBoxFUSE/dtrace -I/tmp/SBo/VirtualBox-5.2.4/include -I/tmp/SBo/VirtualBox-5.2.4/out/linux.amd64/release -DRTPATH_APP
_PRIVATE=\"/usr/share/virtualbox\" -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_REM -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGE
R -DIN_RING3 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DVBOX_WITH_DTRACE -DVBOX_WITH_DTRACE_R3 -D_FILE_OFFSET_BITS=64 -Wp,-MD,/tmp/SBo/VirtualBox-5.2.4/out/linux.amd64/release/obj/VBoxFUSE/VBoxFUSE.o.dep -Wp,-MT,/tmp/SBo/VirtualBox-
5.2.4/out/linux.amd64/release/obj/VBoxFUSE/VBoxFUSE.o -Wp,-MP -o /tmp/SBo/VirtualBox-5.2.4/out/linux.amd64/release/obj/VBoxFUSE/VBoxFUSE.o /tmp/SBo/VirtualBox-5.2.4/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp
If this don't fit in this thread (I supposed it don't) I will open another, to take help with this.
Hydrogen failed to build for me unless Raptor is installed. Raptor isn't listed as a dependency. I have some of the optional dependencies installed for hydrogen.
hi RadicalDreamer,
is this, by any chance, a current-specific issue?
if it isn't you should report this to the maintainer and to the slackbuilds-users mailing list.
Hi , i cant build vlc , error point to speex package from slackware , cause disable-static ..
/usr/bin/grep: /usr/lib64/libspeex.la: No such file or directory
I think you might rebuild all of the dependencies too, you most probably have one of them linking to a previous version of the speex package (containing libspeex.la).
if you use a single make job and post the full build output maybe I can try to pinpoint it (I cannot guarantee that I will be able to).
I think you might rebuild all of the dependencies too, you most probably have one of them linking to a previous version of the speex package (containing libspeex.la).
if you use a single make job and post the full build output maybe I can try to pinpoint it (I cannot guarantee that I will be able to).
Thanks for point me to this way ... rebuild libshout solved my problem.
I'd like to build the current version of Kicad (nightly build). The OpenCascade Community Edition (OCE) dependency is not in the SBo listing.
Can we insert it into SBo repository ?
every script in our repository is there because there's someone that uses that application/library and wish to maintain it: if you wish to maintain it you are more than welcomed to submit it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
