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.
try applying this diff, that version-bump it to the latest and applies also a couple of little fixes.
Hi Ponce, now the software compiled without any problems and I was able to spin it for a quick run, which was also trouble-free. So I would say that your changes solved the problem. Thank you!!
This might be off-topic, but VeraCrypt has issued a priority release (1.19), and its compilation fails under current. After editing the corresponding SlackBuild, here is the relevant output:
Code:
Compiling cpu.c
In file included from ../Crypto/cpu.h:154:0,
from ../Crypto/cpu.c:3:
../Crypto/cpu.c: In function ‘TryAESNI’:
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/include/wmmintrin.h:61:1: error: inlining failed in call to always_inline ‘_mm_aesenc_si128’: target specific option mismatch
_mm_aesenc_si128 (__m128i __X, __m128i __Y)
^
../Crypto/cpu.c:232:14: error: called from here
ciphered = _mm_aesenc_si128(block, subkey);
^
In file included from ../Crypto/cpu.h:154:0,
from ../Crypto/cpu.c:3:
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/include/wmmintrin.h:61:1: error: inlining failed in call to always_inline ‘_mm_aesenc_si128’: target specific option mismatch
_mm_aesenc_si128 (__m128i __X, __m128i __Y)
^
../Crypto/cpu.c:232:14: error: called from here
ciphered = _mm_aesenc_si128(block, subkey);
^
/tmp/SBo/VeraCrypt-1.19/src/Build/Include/Makefile.inc:20: recipe for target '../Crypto/cpu.o' failed
make[1]: *** [../Crypto/cpu.o] Error 1
Makefile:340: recipe for target 'all' failed
make: *** [all] Error 2
This might be off-topic, but VeraCrypt has issued a priority release (1.19), and its compilation fails under current. After editing the corresponding SlackBuild, here is the relevant output:
Code:
Compiling cpu.c
In file included from ../Crypto/cpu.h:154:0,
from ../Crypto/cpu.c:3:
../Crypto/cpu.c: In function ‘TryAESNI’:
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/include/wmmintrin.h:61:1: error: inlining failed in call to always_inline ‘_mm_aesenc_si128’: target specific option mismatch
_mm_aesenc_si128 (__m128i __X, __m128i __Y)
^
../Crypto/cpu.c:232:14: error: called from here
ciphered = _mm_aesenc_si128(block, subkey);
^
In file included from ../Crypto/cpu.h:154:0,
from ../Crypto/cpu.c:3:
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/include/wmmintrin.h:61:1: error: inlining failed in call to always_inline ‘_mm_aesenc_si128’: target specific option mismatch
_mm_aesenc_si128 (__m128i __X, __m128i __Y)
^
../Crypto/cpu.c:232:14: error: called from here
ciphered = _mm_aesenc_si128(block, subkey);
^
/tmp/SBo/VeraCrypt-1.19/src/Build/Include/Makefile.inc:20: recipe for target '../Crypto/cpu.o' failed
make[1]: *** [../Crypto/cpu.o] Error 1
Makefile:340: recipe for target 'all' failed
make: *** [all] Error 2
Yeah I am stumped by this too. I do not have a working build yet and it frustrates me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.