Bug 1225796 - Package libcomps does not build with gcc14 because of new errors
Summary: Package libcomps does not build with gcc14 because of new errors
Status: RESOLVED DUPLICATE of bug 1221700
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: modern_C
  Show dependency treegraph
 
Reported: 2024-06-02 10:03 UTC by Martin Jambor
Modified: 2024-06-02 11:27 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Jambor 2024-06-02 10:03:20 UTC
GCC 14 newly by default treats as errors a number of situations which
before were only warnings.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

Because of this, package libcomps fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/libcomps/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

According to
https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/l/libcomps.md?ref_type=heads
we perhaps need https://github.com/rpm-software-management/libcomps/commit/a71bce7e62990550a57688e51b14eb82d6de196b

The (first) error (that halts the build) is:

[   11s] /home/abuild/rpmbuild/BUILD/libcomps-0.1.20/libcomps/tests/check_parse.c:588:11: error: assignment to ‘COMPS_DocGroup *’ from incompatible pointer type ‘COMPS_DocCategory *’ [-Wincompatible-pointer-types]
[   11s]   588 |         g = (COMPS_DocCategory*)it->comps_obj;
[   11s]       |           ^
Comment 1 Martin Jambor 2024-06-02 11:27:03 UTC
Again I forgot to check the list of already submitted bugs, this has already been filed as bug#1221700.

*** This bug has been marked as a duplicate of bug 1221700 ***