Bug 1525884 - thrift-0.10.0-4.fc27 FTBFS: src/ext/module.cpp:20:10: fatal error: Python.h: No such file or directory
Summary: thrift-0.10.0-4.fc27 FTBFS: src/ext/module.cpp:20:10: fatal error: Python.h: ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: thrift
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Tubbs
QA Contact: Fedora Extras Quality Assurance
URL: https://apps.fedoraproject.org/kosche...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-14 10:11 UTC by Petr Pisar
Modified: 2017-12-22 03:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-22 03:44:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2017-12-14 10:11:15 UTC
thrift-0.10.0-4.fc27 fails to build in F27:

building 'thrift.protocol.fastbinary' extension
creating build/temp.linux-aarch64-3.6
creating build/temp.linux-aarch64-3.6/src
creating build/temp.linux-aarch64-3.6/src/ext
gcc -pthread -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -D_GNU_SOURCE -fPIC -fwrapv -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fPIC -Isrc -I/usr/include/python3.6m -c src/ext/module.cpp -o build/temp.linux-aarch64-3.6/src/ext/module.o
src/ext/module.cpp:20:10: fatal error: Python.h: No such file or directory
 #include <Python.h>
          ^~~~~~~~~~

It happens probably since this change <https://apps.fedoraproject.org/koschei/build/3727497>.

Comment 1 Christopher Tubbs 2017-12-22 03:44:36 UTC
Can not reproduce this error from koschei. It looks like it was probably a temporarily broken buildroot.


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