Bug 1817704

Summary:	python-logbook fails to build with Python 3.9: No such file or directory: 'gcc'
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	python-logbook	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	cstratak, gwync, mail, mhroncok, mplch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-26 20:11:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1785415

Description Miro Hrončok 2020-03-26 19:13:27 UTC

python-logbook fails to build with Python 3.9.0a5.

running build_ext
building 'logbook._speedups' extension
creating build/temp.linux-x86_64-3.9
creating build/temp.linux-x86_64-3.9/logbook
gcc ... -fPIC -I/usr/include/python3.9 -c logbook/_speedups.c -o build/temp.linux-x86_64-3.9/logbook/_speedups.o
error: [Errno 2] No such file or directory: 'gcc'

I wonder how was this previously built successfully on rawhide without gcc.


For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01321093-python-logbook/

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

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 1 Gwyn Ciesla 2020-03-26 20:11:08 UTC

I'm guessing one of it's BRs BRed it and then didn't.

Or maybe it was gnomes. You never know.

Anyway, fixed.

Comment 2 Miro Hrončok 2020-03-26 21:22:18 UTC

I've checked the previous root.logs. gcc was not present. So I guess gnomes.



Anyway, the extension module is still not built:

running build_ext
***************************************************************************
WARNING: The C extension could not be compiled, speedups are not enabled.
Plain-Python build succeeded.
***************************************************************************


I guess that missing gcc was previously considered such failure and now it isn't, but there is another failure.

Feel free to investigate if you want the speedups, or not.

Thanks for the fix.

Comment 3 Gwyn Ciesla 2020-03-27 13:55:29 UTC

Odd. It's failing because a source file is missing. Oh well. Thanks!