Bug 2045745

Summary: kdelibs: FTBFS in Fedora rawhide/f36
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: kdelibsAssignee: Than Ngo <than>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jgrulich, jreznik, kde-sig, kevin, me, rdieter, smparrish, than
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: 2022-02-03 15:09:54 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:    
Bug Blocks: 1992484    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2022-01-25 18:29:13 UTC
kdelibs failed to build from source in Fedora rawhide/f36

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix kdelibs 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,
kdelibs will be orphaned. Before branching of Fedora 37,
kdelibs 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 2022-01-25 18:29:16 UTC
Created attachment 1855067 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2022-01-25 18:29:18 UTC
Created attachment 1855068 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-01-25 18:29:19 UTC
Created attachment 1855069 [details]
state.log

Comment 4 Kevin Kofler 2022-01-25 19:45:23 UTC
{standard input}: Assembler messages:
{standard input}:47076: Error: junk at end of line, first unrecognized character is `-'
{standard input}:47077: Error: expected comma after "operator"
{standard input}:49045: Error: junk at end of line, first unrecognized character is `-'
{standard input}:49046: Error: expected comma after "operator"
{standard input}:49553: Error: junk at end of line, first unrecognized character is `-'
{standard input}:49554: Error: expected comma after "operator"
{standard input}:49965: Error: junk at end of line, first unrecognized character is `-'
{standard input}:49966: Error: expected comma after "operator"
{standard input}:51159: Error: junk at end of line, first unrecognized character is `-'
{standard input}:51160: Error: expected comma after "operator"
{standard input}:51886: Error: junk at end of line, first unrecognized character is `-'
{standard input}:51887: Error: expected comma after "operator"
{standard input}:52695: Error: junk at end of line, first unrecognized character is `-'
{standard input}:52696: Error: expected comma after "operator"
{standard input}:53620: Error: junk at end of line, first unrecognized character is `-'
{standard input}:53621: Error: expected comma after "operator"
{standard input}:54569: Error: junk at end of line, first unrecognized character is `-'
{standard input}:54570: Error: expected comma after "operator"

Looks like something is sending operator- and/or operator-- and/or operator-> to the assembler unmangled.

Comment 5 Than Ngo 2022-02-03 15:09:54 UTC
it is fixed in kdelibs-4.14.38-30.fc36