Bug 2340787

Summary: llvm11: FTBFS in Fedora rawhide/f42
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: llvm11Assignee: Jens Petersen <petersen>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: low    
Version: 42CC: fedora, petersen, sergesanspaille, tstellar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
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: 2300528, 2380784, 2381065, 2381278    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2025-01-22 20:49:49 UTC 
llvm11 failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix llvm11 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,
llvm11 will be orphaned. Before branching of Fedora 43,
llvm11 will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Comment 1 Fedora Release Engineering 2025-01-22 20:49:52 UTC 
Created attachment 2070898 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2025-01-22 20:49:54 UTC 
Created attachment 2070899 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2025-01-22 20:49:55 UTC 
Created attachment 2070900 [details]
state.log
Comment 4 Aoife Moloney 2025-02-26 13:39:18 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.
Comment 5 Jens Petersen 2025-07-21 12:19:02 UTC 
I think it would be okay to retire llvm11 soon: so I don't intend to fix this really.

$ fedora-repoquery --all-archs 43 --whatrequires llvm11*
llvm11-11.1.0-14.fc41.i686 (fedora-rawhide)
llvm11-11.1.0-14.fc41.x86_64 (fedora-rawhide)
llvm11-devel-11.1.0-14.fc41.i686 (fedora-rawhide)
llvm11-devel-11.1.0-14.fc41.x86_64 (fedora-rawhide)
llvm11-doc-11.1.0-14.fc41.noarch (fedora-rawhide)
llvm11-11.1.0-14.fc41.aarch64 (fedora-rawhide-aarch64)
llvm11-devel-11.1.0-14.fc41.aarch64 (fedora-rawhide-aarch64)
llvm11-doc-11.1.0-14.fc41.noarch (fedora-rawhide-aarch64)
llvm11-11.1.0-14.fc41.ppc64le (fedora-rawhide-ppc64le)
llvm11-devel-11.1.0-14.fc41.ppc64le (fedora-rawhide-ppc64le)
llvm11-doc-11.1.0-14.fc41.noarch (fedora-rawhide-ppc64le)
llvm11-11.1.0-14.fc41.s390x (fedora-rawhide-s390x)
llvm11-devel-11.1.0-14.fc41.s390x (fedora-rawhide-s390x)
llvm11-doc-11.1.0-14.fc41.noarch (fedora-rawhide-s390x)