Bug 2336268

Summary: adanaxisgpl fails to build wtih C23 ("error: conflicting types for 'vsnprintf'; have 'int(void)'")
Product: [Fedora] Fedora Reporter: Dave Malcolm <dmalcolm>
Component: adanaxisgplAssignee: Hans de Goede <hans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 42CC: hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: adanaxisgpl-1.2.5-53.fc44 adanaxisgpl-1.2.5-53.fc43 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-09-28 16:04:30 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: 2333037    

Description Dave Malcolm 2025-01-07 22:58:24 UTC
I'm experimentally rebuilding rawhide with the not-yet-released GCC 15 to see if anything breaks, and to help write the porting guide.  See https://fedoraproject.org/wiki/User:Dmalcolm/gcc-15

My test build with GCC 15 failed:
https://copr.fedorainfracloud.org/coprs/dmalcolm/gcc-15-smoketest-3.failed/build/8476064/

whereas my test build with GCC 14 succeeded:
https://copr.fedorainfracloud.org/coprs/dmalcolm/gcc-15-smoketest-3.failed.checker/build/8477649/

Looking at the failure logs e.g.
https://download.copr.fedorainfracloud.org/results/dmalcolm/gcc-15-smoketest-3.failed/fedora-rawhide-x86_64/08476064-adanaxisgpl/builder-live.log.gz

I see:

MushRuby/missing.h:163:12: error: conflicting types for 'vsnprintf'; have 'int(void)'
  163 | extern int vsnprintf _((char *, size_t n, char const *, va_list));
      |            ^~~~~~~~~
In file included from /usr/include/features.h:524,
                 from /usr/include/bits/libc-header-start.h:33,
                 from /usr/include/stdlib.h:26,
                 from MushRuby/ruby.h:52:
/usr/include/bits/stdio2.h:93:1: note: previous definition of 'vsnprintf' with type 'int(char *, long unsigned int,  const char *, __va_list_tag *)'
   93 | __NTH (vsnprintf (__fortify_clang_overload_arg (char *, __restrict, __s),
      | ^~~~~

This is probably due to GCC 15 now defaulting to -std=gnu23, whereas GCC 14 defaulted to -std=gnu17, and C23 is stricter about function prototypes than C17.  It's probably fixable by fixing the function prototypes (or by manually adding -std=gnu17 to the C build flags)



Reproducible: Always

Comment 1 Aoife Moloney 2025-02-26 13:21:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 2 Fedora Update System 2025-09-28 16:01:28 UTC
FEDORA-2025-cd428a30f6 (adanaxisgpl-1.2.5-53.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-cd428a30f6

Comment 3 Fedora Update System 2025-09-28 16:04:30 UTC
FEDORA-2025-cd428a30f6 (adanaxisgpl-1.2.5-53.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2025-09-28 17:33:34 UTC
FEDORA-2025-69fc3e0d57 (adanaxisgpl-1.2.5-53.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-69fc3e0d57

Comment 5 Fedora Update System 2025-09-29 02:01:32 UTC
FEDORA-2025-69fc3e0d57 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-69fc3e0d57`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-69fc3e0d57

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-10-07 00:18:55 UTC
FEDORA-2025-69fc3e0d57 (adanaxisgpl-1.2.5-53.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.