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.
I tried to build vbox on an old virtualized -current (20170704) and it works well. Therefore, I checked existing changes between my old current and -current, and the issue is due to a change done in latest glibc (2.25 vs 2.26), and more precisely the following change in /usr/include/sys/ucontext.h :
Code:
/* Number of general registers. */
-#define NGREG 23
+#define __NGREG 23
+#ifdef __USE_MISC
+# define NGREG __NGREG
+#endif
This change leads to the conflicting types in VBoxDTraceTypes.h.
The attached patch Attachment 25801 (see below) fixes this issue.
Hi ponce I have mailed the maintainer; but on my previous computer I did not run into problems compiling openBlas (also on current though); Possibly the processor on my new computer is released after version 0.2.11 of openBlas on Slackbuilds.org.
I found that a a new version of Kicad 4.0.7 just emerged about a month ago.
I tried to compile it, but I went into wxwidgets/wxpython dependency mess ...
How can we do it properly ?
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,560
Rep:
Can't get FreeCAD built on slackware-current, it's ok on slackware-14.2. Here is the error:
---------------------
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/WorkbenchPyImp.cpp.o
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/SelectionObjectPyImp.cpp.o
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/SelectionObject.cpp.o
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/Selection.cpp.o
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/SelectionFilter.cpp.o
[ 31%] Building CXX object src/Gui/CMakeFiles/FreeCADGui.dir/PreCompiled.cpp.o
make[2]: *** Aucune r�gle pour fabriquer la cible ��/usr/lib/libspnav.so��, n�cessaire pour ��lib/libFreeCADGui.so��. Arr�t.
make[1]: *** [CMakeFiles/Makefile2:4493: src/Gui/CMakeFiles/FreeCADGui.dir/all] Error 2
make: *** [Makefile:130: all] Error
-----------------------------
libspnav is installed but doesn't it.
Did you generate the queue file before running above command?
if you are running -current, some dependencies might not build, ast least numpy.
You need to have a look at this commit
FYI, I've just tested building FreeCAD and all of its dependencies using the unofficial repository linked in the first post on two clean full installs, one of slackware-current and the other of slackware64-current, and it went fine in both cases: are you using a different setup from the one I just tested building the stuff onto?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.