Bug 1863702 - pocl: FTBFS in Fedora rawhide/f33
Summary: pocl: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pocl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabian Deutsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 17:13 UTC by Fedora Release Engineering
Modified: 2020-08-04 11:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-04 11:07:52 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (19.28 KB, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
state.log (945 bytes, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2020-08-03 17:13:20 UTC 
pocl failed to build from source in Fedora rawhide/f33

https://koji.fedoraproject.org/koji/taskinfo?taskID=47964296


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix pocl at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
pocl will be orphaned. Before branching of Fedora 34,
pocl will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Fedora Release Engineering 2020-08-03 17:13:22 UTC 
Created attachment 1704629 [details]
build.log
Comment 2 Fedora Release Engineering 2020-08-03 17:13:23 UTC 
Created attachment 1704630 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2020-08-03 17:13:25 UTC 
Created attachment 1704631 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.