Bug 1225907 - Package openssl-1_1 does not build with gcc14 because of new errors
Summary: Package openssl-1_1 does not build with gcc14 because of new errors
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Network (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Martin Jambor
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: modern_C
  Show dependency treegraph
 
Reported: 2024-06-04 09:33 UTC by Martin Jambor
Modified: 2024-07-12 11:52 UTC (History)
1 user (show)

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-04 09:33:12 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 openssl-1_1 fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/openssl-1_1/standard/x86_64

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

It seems we need
https://github.com/openssl/openssl/commit/f9e578e720bb35228948564192adbe3bc503d5fb

See also
https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/o/openssl1.1.md?ref_type=heads
and 

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

[   20s] crypto/evp/c_alld.c: In function 'openssl_add_all_digests_int':
[   20s] crypto/evp/c_alld.c:24:26: error: implicit declaration of function 'fips_in_post' [-Wimplicit-function-declaration]
[   20s]    24 |     if (!FIPS_mode() && !fips_in_post()) {
[   20s]       |                          ^~~~~~~~~~~~
Comment 1 Martin Jambor 2024-06-18 16:11:50 UTC
https://build.opensuse.org/request/show/1181542
Comment 2 Chenzi Cao 2024-07-01 09:45:00 UTC
Hi Martin, you already submitted request for this bug report, so I assign it to you now. Please feel free to reassign whenever necessary, thanks.
Comment 3 Martin Jambor 2024-07-12 11:52:36 UTC
The fix has reached factory.