Bug 2209678

Summary: Can we stop building gcc.i686 and libstdc++-docs.i686?
Product: [Fedora] Fedora Reporter: Václav Kadlčík <vkadlcik>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: dmalcolm, fweimer, jakub, jlaw, jwakely, mcermak, mpolacek, msebor, nickc, sipoyare
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 21:12:15 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:

Description Václav Kadlčík 2023-05-24 13:29:48 UTC
If I am not mistaken, Fedora doesn't *ship* gcc.i686 nor libstdc++-docs.i686.
The are built though, see e.g. gcc-13.1.1-3.fc39 [1], they just get discarded
somewhere later in the pipeline before landing in Fedora repos.

I'd like to have them removed sooner, in the build phase (do not build them
or delete them at the end). They are troublemakers from several points of view:

1. They conflict with their x86_64 counterparts. As a consequence, any time
   you download a full GCC build like
       koji download-build --arch={x86_64,i686,noarch} <build>
   you have to remove the two RPMs before trying to install the build. And
   this workaround has to be applied in every setup script over and over
   again.

1. They significantly slowdown distro-wide automatic tests like
   fedora-ci.koji-build.rpmdeplint.functional [2]. That particular test is
   very sensitive to amount of the files present in the RPMs being tested.
   I believe that not testing libstdc++-docs.i686 will shave 30-40% of the
   test time, possibly preventing timeouts like the one observed in [2].

Thanks for considering!

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2203015
[2] https://artifacts.dev.testing-farm.io/7eb9da00-48cd-4c25-876b-abad7033f7f4

Reproducible: Always

Comment 1 Jonathan Wakely 2023-05-24 13:32:26 UTC
libstdc++-docs is slow to build, so skipping that for the i686 builds would speed them up.

Comment 2 Florian Weimer 2023-05-24 13:34:42 UTC
This is not how Koji works. We need gcc.i686 in the Koji buildroot, so we have to build it, otherwise the i686 builders will not work.

I do not think we need libstdc++-docs on the builders, so we could probably drop it.

Comment 3 Václav Kadlčík 2023-05-24 13:47:34 UTC
Ah, of course, the buildroot :-) Thanks for reminding me!
I hope dropping libstdc++-docs.i686 is feasible.

Comment 4 Jakub Jelinek 2023-05-24 13:50:08 UTC
Yeah.  All the gcc* subpackages of gcc + libstdc++-docs are non-multilib, they need to be built for the 32-bit buildroot to function, but for any of the composes, they should be only included from the primary arch (x86_64 in the x86-64 case).
I don't think libstdc++-docs is worth bothering with in the spec file, it isn't slow compared to the hours of lto profiled bootstrap and make check.

Comment 5 Fedora Release Engineering 2023-08-16 08:09:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 6 Aoife Moloney 2024-11-08 10:52:40 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
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
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Aoife Moloney 2024-11-27 21:12:15 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.