Bug 2143591

Summary: fcgi: Adjustments for building without implicit function declarations
Product: [Fedora] Fedora Reporter: Florian Weimer <fweimer>
Component: fcgiAssignee: Florian Weimer <fweimer>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ktdreyer, zonexpertconsulting
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: fcgi-2.4.0-45.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-17 10:56:14 UTC Type: Bug
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: 2141798    
Attachments:
Description Flags
fcgi-configure-exit.patch none

Description Florian Weimer 2022-11-17 10:21:13 UTC
The fcgi configure scripts were built with an old autoconf version which uses an implicit declaration of exit.

The fcgi upstream site appears to be down (for many years), so it has to be a downstream-only patch.

Comment 1 Florian Weimer 2022-11-17 10:55:51 UTC
Created attachment 1924965 [details]
fcgi-configure-exit.patch

This appears to be the most straightforward fix. It works with libstdc++.

Comment 2 Andrew Bauer 2022-11-17 13:07:18 UTC
Thanks for doing the work, but could you provide some additional background?

I get the general problem behind function declarations:
https://stackoverflow.com/questions/9182763/implicit-function-declarations-in-c

However, what drove you to address this? I didn't see any build failure notices for this package prior to the patch. Did you just want to remove the warnings that gcc likely was giving during the build, or was there some other, specific issue this addressed?

...or is there an upcoming change to the fedora build environment, such as enforcing C99, which would cause this to fail the build?

I am trying to get a better understanding, to determine whether the EPEL branches should receive this patch as well.

Comment 3 Florian Weimer 2022-11-17 13:12:45 UTC
It's related to:

  https://fedoraproject.org/wiki/Changes/PortingToModernC
  https://fedoraproject.org/wiki/Toolchain/PortingToModernC

It's in preparation of a potential change in GCC 14. In a few cases (probably this one), we have to patch packages to silence the reports (which I'm still trying to get off the ground, I'll update the second wiki page once I've got details).

Comment 4 Andrew Bauer 2022-11-17 13:18:13 UTC
Perfect. Thank you for explaining.

Comment 5 Florian Weimer 2022-11-18 08:19:03 UTC
Sorry, I botched my testing and missed another implicit exit declaration. Should be fixed now.