Bug ID 1224533
Summary Package alpine does not build with gcc 14 because of a call arguments with an incompatible pointer type
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee screening-team-bugs@suse.de
Reporter mjambor@suse.com
QA Contact qa-bugs@suse.de
Blocks 1220571
Target Milestone ---
Found By ---
Blocker ---

Package alpine fails to build with gcc 14, which newly treats as
errors a number of situations which before were mere warnings.  More
information can be found at https://gcc.gnu.org/gcc-14/porting_to.html
and in bug #1220571.

The failure can be seen online for example at
https://build.opensuse.org/package/live_build_log/home:rguenther:plgrnd/alpine/openSUSE_Factory/x86_64
and be reproduced locally with osc build --clean --alternative-project
home:rguenther:nextgcc

The error which stops the build is:

[   68s] adrbklib.c: In function ‘sort_addr_list’:
[   68s] adrbklib.c:4705:64: error: passing argument 4 of ‘qsort’ from
incompatible pointer type [-Wincompatible-pointer-types]
[   68s]  4705 |     qsort((qsort_t *)list, (size_t)(p - list), sizeof(char *),
cmp_addr);
[   68s]       |                                                               
^~~~~~~~
[   68s]       |                                                               
|
[   68s]       |                                                               
int (*)(const char *, const char *)
[   68s] In file included from ../include/system.h:42,
[   68s]                  from ../pith/headers.h:25,
[   68s]                  from adrbklib.c:14:
[   68s] /usr/include/stdlib.h:971:34: note: expected ‘__compar_fn_t’ {aka ‘int
(*)(const void *, const void *)’} but argument is of type ‘int (*)(const char
*, const char *)’
[   68s]   971 |                    __compar_fn_t __compar) __nonnull ((1, 4));


Interestingly, I while I find see Gentoo and Fedore bugs (see the
links in the meta bug) about alpine not compiling with compilers with
this strict behavior, none of them look like the issue above.


You are receiving this mail because: