From: Carlos O'Donell <carlos@redhat.com>
To: Matheus Castanho <msc@linux.ibm.com>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v12 1/2] Add 'codepoint_collation' support for LC_COLLATE.
Date: Mon, 20 Sep 2021 08:54:48 -0400 [thread overview]
Message-ID: <1f64c97e-c083-244e-609b-d2260ab982c3@redhat.com> (raw)
In-Reply-To: <878rzrwgwa.fsf@linux.ibm.com>
On 9/20/21 08:49, Matheus Castanho wrote:
>
> Carlos O'Donell <carlos@redhat.com> writes:
>
>> On 9/6/21 1:20 PM, Matheus Castanho wrote:
>>> In file included from C-collate.c:22:
>>> C-collate-seq.c:58:42: error: expected ‘,’ before ‘)’ token
>>> _Static_assert (sizeof (collseqmb) == 256);
>>> ^
>>
>> Which version of gcc? I assume gcc 8.x? Which distro? I know Florian
>> fixed this, but I'm curious what you're using.
>>
>> So DJ and I just talked about how we would catch this in CI/CD, but
>> we'd have to run fairly old unsupported Fedora to test this, so we'd
>> have to do something different.
>
> Sorry for the delay. One case where I saw it was using GCC from Debian
> 10:
>
> $ gcc --version
> gcc (Debian 8.3.0-6) 8.3.0
> [...]
Yea, so that's old enough that it would trigger the failure. Thanks, Florian fixed this
with commit c9fef4b7d1d0f2dad192c74f06102752247677a9, and we shouldn't regress again
thanks to the requirement for 2 arguments.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-09-20 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:43 [PATCH v12 0/2] C.UTF-8 Carlos O'Donell
2021-09-06 15:43 ` [PATCH v12 1/2] Add 'codepoint_collation' support for LC_COLLATE Carlos O'Donell
2021-09-06 17:20 ` Matheus Castanho
2021-09-06 17:28 ` Florian Weimer
2021-09-07 1:28 ` Carlos O'Donell
2021-09-07 1:57 ` Carlos O'Donell
2021-09-20 12:49 ` Matheus Castanho
2021-09-20 12:54 ` Carlos O'Donell [this message]
2021-09-06 15:43 ` [PATCH v12 2/2] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell
2022-01-26 2:44 ` Michael Hudson-Doyle
2022-01-28 16:42 ` Carlos O'Donell
2022-01-30 23:58 ` Michael Hudson-Doyle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f64c97e-c083-244e-609b-d2260ab982c3@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).