[SOLVED] Problem with libsodium on -current64 (sbopkg)

konmit · 04-01-2016, 05:34 AM

Hello!

I'm trying to build uTox package with sbopkg (master branch repo),
but building libsodium seems like quite a challenge on -current 64.
After several attempts with queue files

Code:

usr/doc/sbopkg-0.37.1/contrib/sqg -p uTox

I've tried with the latest source (libsodium-1.0.8) and changed the SlackBuild script accordingly, but had no luck.
Here's an error output:

Code:

CC       randombytes/salsa20/libsodium_la-randombytes_salsa20_random.lo
In file included from /usr/include/sys/syscall.h:31:0,
                 from randombytes/salsa20/randombytes_salsa20_random.c:9:
randombytes/salsa20/randombytes_salsa20_random.c: In function ‘_randombytes_linux_getrandom’:
randombytes/salsa20/randombytes_salsa20_random.c:180:26: error: ‘__NR_getrandom’ undeclared (first use in this function)
         readnb = syscall(SYS_getrandom, buf, (int) size, 0);
                          ^
randombytes/salsa20/randombytes_salsa20_random.c:180:26: note: each undeclared identifier is reported only once for each function it appears in
Makefile:2620: recipe for target 'randombytes/salsa20/libsodium_la-randombytes_salsa20_random.lo' failed
make[3]: *** [randombytes/salsa20/libsodium_la-randombytes_salsa20_random.lo] Error 1
make[3]: Leaving directory '/tmp/SBo/libsodium-1.0.8/src/libsodium'
Makefile:2967: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/libsodium-1.0.8/src/libsodium'
Makefile:377: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libsodium-1.0.8/src'
Makefile:491: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

This is beyond my current knowledge and skills, so any experienced advice
on this matter would be much appreciated.
Thanks!

55020 · 04-01-2016, 06:22 AM

Any good reason for using libsodium-1.0.8 instead of 1.0.7?

If you are using the git master, you should have the following versions (if you don't, you're not configuring or using sbopkg correctly). Build them in this order:

OpenAL-1.17.1
libfilteraudio-20150516
opus-1.1.2
libsodium-1.0.7
toxcore-20160214
uTox-0.5.0

FWIW, I built these most recently on 29/30 March, using -current from 27 March, and they all built ok.

konmit · 04-01-2016, 07:31 AM

Thanks for your reply, 55020.

The reason for using libsodium-1.0.8 to build a package was a message that appeared after second failure,
something like "maybe you are using outdated libs". After that I tried to build it 'manually' but the same error occurred.

Yes, that's the order from my queue file. Maybe I'm missing something related to sbopkg.conf file?
I only changed these lines:

Code:

# Other variables:
REPO_BRANCH=${REPO_BRANCH:-master}
REPO_NAME=${REPO_NAME:-SBo}

Skaendo · 04-01-2016, 07:40 AM

Just curious, which version of cmake are you using?

Code:

$ cmake --version

konmit · 04-01-2016, 07:43 AM

Hi, Skaendo.

Code:

bash-4.3# cmake --version
cmake version 3.5.1

Skaendo · 04-01-2016, 07:46 AM

Quote:

Originally Posted by konmit

Hi, Skaendo.

Code:

bash-4.3# cmake --version
cmake version 3.5.1

Same version that I am using.

I am getting failed builds as well, but with different packages. I don't know if it's related, but it is the same fail:

Code:

recipe for target 'all-recursive' failed

ponce · 04-01-2016, 07:55 AM

Code:

CC       randombytes/salsa20/libsodium_la-randombytes_salsa20_random.lo
In file included from /usr/include/sys/syscall.h:31:0,
                 from randombytes/salsa20/randombytes_salsa20_random.c:9:
randombytes/salsa20/randombytes_salsa20_random.c: In function ‘_randombytes_linux_getrandom’:
randombytes/salsa20/randombytes_salsa20_random.c:180:26: error: ‘__NR_getrandom’ undeclared (first use in this function)

hi konmit,

seem like __NR_getrandom is defined in the the kernel-source unistd.h files: are you sure you got a full install of Slackware?

konmit · 04-01-2016, 08:38 AM

Yes, ponce, it's a full install but you made me thinking.

I installed full, clean 14.1-64 and after first boot I pointed mirror to -current64
and commented out kernel lines (huge, modules, source) in /etc/slackpkg/blacklist.
After that I did the following: slackpkg update gpg; slackpkg update, slackpkg install-new; slackpkg upgrade-all;
then 'lilo', reboot and then 'slackpkg clean-system'.
I haven't experienced any problem afterwards, including sbopkg which I used to build e.g. e17 with all dependencies.
Well, it was before Sat Mar 26 when cmake was upgraded.

Thanks for chiming in. :beer:

ponce · 04-01-2016, 10:39 AM

you can try reinstalling the interested packages

Code:

slackpkg update
slackpkg upgrade-all
slackpkg reinstall gcc glibc kernel-headers kernel-source

and be sure that this operation reinstalls all of the following packages in their latest versions (if also others from the gcc-* and glibc-* series are selected should be ok too)

Code:

gcc-5.3.0-x86_64-3.txz
glibc-2.23-x86_64-1.txz
kernel-headers-4.4.6-x86-1.txz
kernel-source-4.4.6-noarch-1.txz

konmit · 04-01-2016, 10:47 AM

Thanks for advice, ponce. Reinstalling now, will report later. :thumbup:

konmit · 04-01-2016, 11:32 AM

Bingo!
Works like a charm. Libsodium and other uTox dependencies built w/o problem.

It seems like old kernel-headers somehow 'survived' previous upgrade.
Thanks a lot @ponce & others who jumped in to help.

Marking this [SOLVED].

Skaendo · 04-01-2016, 12:03 PM

Good to hear that you got it fixed. (Mine isn't but I'm not building any regular packages)

You prefer uTox to qTox? Can I ask why?
I have been using qTox for quite a while now. Never tried uTox but I did look at it when I first started using *Tox and I can't remember why I chose qTox.

konmit · 04-01-2016, 12:14 PM

Hey Skaendo.

Honestly, when I saw qt5 is needed for qTox I decided to try lighter client, uTox.
I just want to test how it works with Antox, Tox client for Android.
Both alphas and I'm afraid they don't speak the same language yet.

Ricin seems to be good and well maintained but it's also 'dependency hungry'.