Bug 1865257

Summary: prusa-slicer: FTBFS in Fedora rawhide/f33 on armv7hl with LTO enabled
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: prusa-slicerAssignee: Jeff Law <law>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 34CC: j, mhroncok
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: 2021-11-05 12:24:02 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: 245418    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2020-08-03 20:44:45 UTC
prusa-slicer failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix prusa-slicer 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,
prusa-slicer will be orphaned. Before branching of Fedora 34,
prusa-slicer 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 20:44:47 UTC
Created attachment 1708954 [details]
build.log

Comment 2 Fedora Release Engineering 2020-08-03 20:44:48 UTC
Created attachment 1708955 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-08-03 20:44:50 UTC
Created attachment 1708956 [details]
state.log

Comment 4 Miro Hrončok 2020-08-04 13:03:18 UTC
The original failure is solved via https://src.fedoraproject.org/rpms/prusa-slicer/c/96833091efa3dec87c8caca4ebcbc13167a2fa0a?branch=master

But now the build fails on armv7hl with:

error: Installed (but unpackaged) file(s) found:
   /usr/bin/prusa-slicer.wrapped.gdb-index-9pY4kY
    Installed (but unpackaged) file(s) found:
   /usr/bin/prusa-slicer.wrapped.gdb-index-9pY4kY

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

The aarch64 and s390x were cancelled, resubmitting again without --fail-fast.

Ask for help: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/IP7NOD5I3OQ7A2VC2FXJVL7KVEZJ5PA7/

Comment 5 Miro Hrončok 2020-08-04 16:33:30 UTC
It's armv7hl only indeed.

Comment 6 Miro Hrončok 2020-08-04 17:53:12 UTC
extracting debug info from /builddir/build/BUILDROOT/prusa-slicer-2.2.0-4.fc33.arm/usr/bin/prusa-slicer.wrapped
../../gdb/utils.c:691: internal-error: virtual memory exhausted: can't allocate 234696314 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
/usr/bin/gdb-add-index: line 106: 22699 Aborted                 (core dumped) $GDB --batch -nx -iex 'set auto-load no' -ex "file $file" -ex "save gdb-index $dwarf5 $dir"

Comment 7 Miro Hrončok 2020-08-04 21:24:48 UTC
FWIW this makes it build:

%ifarch %{arm}
%global _lto_cflags %{nil}
%endif


I'll wait how the devel thread goes and apply it if it goes nowhere.

Comment 8 Miro Hrončok 2020-08-07 09:00:51 UTC
Pushed that as a workaround.

Comment 9 Ben Cotton 2020-08-11 15:04:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 10 Ben Cotton 2021-11-04 17:32:15 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Miro Hrončok 2021-11-05 12:24:02 UTC
I've checked and the workaround is no longer needed on F34+.