Bug 1675181

Summary: jemalloc: FTBFS in Fedora rawhide/f30
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: jemallocAssignee: Ingvar Hagelund <ingvar>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dan, ingvar, lmohanty
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: 2019-03-11 14:14:47 UTC 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: 1677602    
Bug Blocks: 467765, 1674516    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2019-02-11 20:32:58 UTC 
jemalloc failed to build from source in Fedora rawhide/f30

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Please fix jemalloc 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,
jemalloc will be orphaned. Before branching of Fedora 31,
jemalloc 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 2019-02-11 20:33:01 UTC 
Created attachment 1530654 [details]
build.log

file build.log too big, will only attach last 1024 bytes
Comment 2 Fedora Release Engineering 2019-02-11 20:33:03 UTC 
Created attachment 1530655 [details]
root.log

file root.log too big, will only attach last 1024 bytes
Comment 3 Fedora Release Engineering 2019-02-11 20:33:06 UTC 
Created attachment 1530656 [details]
state.log
Comment 4 Ingvar Hagelund 2019-02-14 14:35:11 UTC 
I filed an upstream issue https://github.com/jemalloc/jemalloc/issues/1434

sharkcz, maybe you can help us with this?

Ingvar
Comment 5 Dan Horák 2019-02-14 14:50:38 UTC 
Yes, I'll take a look, adding to my to-do list :-) Must be related to gcc9, I'm running a CI for jemalloc and I'm not aware of any other issues.
Comment 6 Ingvar Hagelund 2019-03-11 14:14:47 UTC 
Rebuilt without problems after #1677602 was fixed. Close.