Bug 2148940 - BitchX: Work around C99 compatibility issues
Summary: BitchX: Work around C99 compatibility issues
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: BitchX
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: kevin_redhat
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PortingToModernCExemptions
TreeView+ depends on / blocked
 
Reported: 2022-11-28 11:49 UTC by Florian Weimer
Modified: 2024-01-15 11:01 UTC (History)
2 users (show)

Fixed In Version: BitchX-1.2.1-33.fc40
Clone Of:
Environment:
Last Closed: 2024-01-15 11:01:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
BitchX-configure-c99.patch (1.87 KB, patch)
2022-11-28 11:49 UTC, Florian Weimer
no flags Details | Diff
BitchX-acro-c99.patch (4.06 KB, patch)
2024-01-04 18:19 UTC, Florian Weimer
no flags Details | Diff
BitchX-aim-c99.patch (3.17 KB, patch)
2024-01-04 18:20 UTC, Florian Weimer
no flags Details | Diff

Description Florian Weimer 2022-11-28 11:49:24 UTC
Created attachment 1928004 [details]
BitchX-configure-c99.patch

To build with future compiler versions, we need to make Fedora packages compatible with stricter C99 build modes. Upstream is largely dormant, so filing this bug for tracking purposes. I found a bunch of upstream patches we can use, only the configure updates are custom.

Comment 1 Florian Weimer 2024-01-04 18:19:34 UTC
This needs many more fixes for GCC 14 compatibility.  Some of them are already in dist-git, but the AIM plugin needs a few more changes. I'm attaching a new version of that, and fixes for the acro plugin.

I do not plan to spend more time on this.

Comment 2 Florian Weimer 2024-01-04 18:19:55 UTC
Created attachment 2007207 [details]
BitchX-acro-c99.patch

Comment 3 Florian Weimer 2024-01-04 18:20:32 UTC
Created attachment 2007208 [details]
BitchX-aim-c99.patch

Comment 4 Florian Weimer 2024-01-15 11:01:51 UTC
I downgraded the C type safety level instead.


Note You need to log in before you can comment on or make changes to this bug.