[Slackbuilds-users] qt5 fails to build

[Andrzej Telszewski]

On 10/01/17 15:25, Andrzej Telszewski wrote:
> Hi,
>
> When trying to build qt5, it fails miserably ;-)
>
> Could it be related to _Wed Dec 28 21:05:19 UTC 2016_ python-2.7.13
> update in Slackware?
>

This certainly looks like something is wrong with the Slackware's update.

Based on:
https://github.com/NixOS/nixpkgs/issues/10092

I reverted to Python 2.7.11 and:

$ python
Python 2.7.11 (default, Mar  3 2016, 13:35:30)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
<RLock(None, 0)>
 >>>

Then I updated to Python 2.7.13 from _patches_ and:

$ python
Python 2.7.13 (default, Dec 28 2016, 13:46:09)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 182, in 
RLock
     from multiprocessing.synchronize import RLock
   File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, 
in <module>
     " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation, 
therefore, the required synchronization primitives needed will not 
function, see issue 3770.
 >>>


I then just rebuilt Python 2.7.13 from _patches_ and:

$ python
Python 2.7.13 (default, Jan 10 2017, 15:45:07)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
<RLock(None, 0)>
 >>>


Somebody calls Pat?

-- 
Best regards,
Andrzej Telszewski