Bug 1225855 - Package liblogging does not build with gcc14 because of new errors
Summary: Package liblogging does not build with gcc14 because of new errors
Status: RESOLVED DUPLICATE of bug 1221715
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-03 14:48 UTC by Martin Jambor
Modified: 2024-06-03 14:58 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-03 14:48:02 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 liblogging fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/liblogging/standard/x86_64

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

The corresponding Gentoo bug seems to be:
https://bugs.gentoo.org/926515

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

[   10s] beepframe.c:170:1: error: return type defaults to ‘int’ [-Wimplicit-int]
[   10s]   170 | sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan)
[   10s]       | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[   10s] beepmessage.c: In function ‘sbMIMEExtract’:
[   10s] beepmessage.c:140:15: warning: variable ‘pHdr’ set but not used [-Wunused-but-set-variable]
[   10s]   140 |         char* pHdr;
[   10s]       |               ^~~~
Comment 1 Martin Jambor 2024-06-03 14:58:37 UTC
Duplicate of bug#1221715

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