Bug 1831237 - Io-language fails to build in rawhide: fatal error: sys/sysctl.h: No such file or directory
Summary: Io-language fails to build in rawhide: fatal error: sys/sysctl.h: No such fil...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Io-language
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON39 F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-05-04 18:04 UTC by Miro Hrončok
Modified: 2020-05-04 20:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-04 19:58:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2020-05-04 18:04:29 UTC
Io-language fails to build:

/builddir/build/BUILD/io-e64ff9/libs/iovm/source/IoSystem.c:26:11: fatal error: sys/sysctl.h: No such file or directory
   26 | # include <sys/sysctl.h>
      |           ^~~~~~~~~~~~~~
compilation terminated.

This affects the Python 3.9 rebuild, but also happens in rawhide.

See https://koschei.fedoraproject.org/package/Io-language

For the build logs with Python 3.9, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01365369-Io-language/

For all our attempts to build Io-language with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/Io-language/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 2 Miro Hrončok 2020-05-04 20:38:24 UTC
Thanks!


Note You need to log in before you can comment on or make changes to this bug.