pyca / pyca/pynacl

PyNaCl Build Failure on Solaris 10: make check Fails During randombytes Test

Open
#832 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.2k
Forks
267
Avg merge
42m
Merged PRs (30d)
2

Description

Environment:

•	OS: Solaris 10 (SunOS 5.10)
•	Architecture: x86_64
•	GCC Version: 9.5.0
•	Python Version: 3.11
•	PyNaCl Version: 1.4.0 (attempting to build from source)
•	libsodium Version: 1.0.18 (built from source)

Issue Summary:

I am attempting to install PyNaCl on a Solaris 10 system, but the build process fails during the make check step. The failure occurs in the randombytes test, which results in the overall test suite failing with a non-zero exit status.

PASS: aead_aes256gcm
PASS: aead_aes256gcm2
PASS: aead_chacha20poly1305
...
FAIL: randombytes
...

Testsuite summary for libsodium 1.0.18

TOTAL: 77

PASS: 76

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

============================================================================
See test/default/test-suite.log
Please report to https://github.com/jedisct1/libsodium/issues

make[4]: *** [Makefile:1776: test-suite.log] Error 1
make[4]: Leaving directory '/usr/PyNaCl-1.4.0/build/temp.solaris-2.10-i86pc.64bit-cpython-311/test/default'
make[3]: *** [Makefile:1884: check-TESTS] Error 2
make[3]: Leaving directory '/usr/PyNaCl-1.4.0/build/temp.solaris-2.10-i86pc.64bit-cpython-311/test/default'
make[2]: *** [Makefile:2490: check-am] Error 2
make[2]: Leaving directory '/usr/PyNaCl-1.4.0/build/temp.solaris-2.10-i86pc.64bit-cpython-311/test/default'
make[1]: *** [Makefile:402: check-recursive] Error 1
make[1]: Leaving directory '/usr/PyNaCl-1.4.0/build/temp.solaris-2.10-i86pc.64bit-cpython-311/test'
make: *** [Makefile:514: check-recursive] Error 1
Traceback (most recent call last):
File "/usr/PyNaCl-1.4.0/setup.py", line 216, in
setup(
...
subprocess.CalledProcessError: Command '['make', 'check']' returned non-zero exit status 2.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with libsodium's test/default/test-suite.log and the failing randombytes test to identify why it fails on Solaris 10. Then inspect PyNaCl's setup.py around the make check invocation; done means the dependency checks pass and PyNaCl builds successfully from source on the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, python
Domain
build-system, cryptography
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.