--- Begin Message ---
Subject: |
Compilation failure of 27.2 on ppc64le |
Date: |
Mon, 24 Jan 2022 12:11:23 -0500 (EST) |
User-agent: |
Alpine 2.22 (DEB 394 2020-01-19) |
Hi,
On Fedora, we're seeing a compile error when compiling 27.2 on ppc64le
architecture. Log excerpt below, full log at [1]:
CC regex.o
In file included from /usr/include/stdio.h:899,
from ./stdio.h:43,
from ../../lib/regex_internal.h:24,
from ../../lib/regex.c:68:
/usr/include/bits/stdio-ldbl.h: In function '__LDBL_REDIR1_DECL':
/usr/include/bits/stdio-ldbl.h:36:1: error: expected declaration
specifiers before '__LDBL_REDIR1_DECL'
36 | __LDBL_REDIR1_DECL (scanf, __isoc99_scanfieee128)
| ^~~~~~~~~~~~~~~~~~
In file included from /usr/include/features.h:488,
from /usr/include/errno.h:25,
from ../../lib/libc-config.h:39,
from ../../lib/regex.c:21:
/usr/include/bits/stdio-ldbl.h:86:1: error: storage class specified for
parameter '__sprintf_chk'
86 | __LDBL_REDIR2_DECL (sprintf_chk)
| ^~~~~~~~~~~~~~~~~~
/usr/include/bits/stdio-ldbl.h:87:1: error: storage class specified for
parameter '__vsprintf_chk'
87 | __LDBL_REDIR2_DECL (vsprintf_chk)
| ^~~~~~~~~~~~~~~~~~
/usr/include/bits/stdio-ldbl.h:89:1: error: storage class specified for
parameter '__snprintf_chk'
89 | __LDBL_REDIR2_DECL (snprintf_chk)
| ^~~~~~~~~~~~~~~~~~
/usr/include/bits/stdio-ldbl.h:90:1: error: storage class specified for
parameter '__vsnprintf_chk'
90 | __LDBL_REDIR2_DECL (vsnprintf_chk)
| ^~~~~~~~~~~~~~~~~~
Possibly related to 128-bit long double? gnulib out of sync with glibc?
[1] https://kojipkgs.fedoraproject.org//work/tasks/1829/81671829/build.log
Thanks,
Scott
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#53509: Compilation failure of 27.2 on ppc64le |
Date: |
Tue, 5 Sep 2023 18:56:48 -0700 |
Eli Zaretskii <eliz@gnu.org> writes:
>> Yep, 28.0.91 appears to build fine on ppc64le with GCC 12. Any idea what
>> commit fixed it, or do I need to bisect? :)
>
> Sorry, no idea, but I'd start by comparing the Gnulib files involved
> in this.
It seems like the issue here has been resolved, so I'm closing this bug.
--- End Message ---