From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: bug-gnulib@gnu.org
Subject: Re: FAIL in diffutils/gnulib-tests
Date: Tue, 7 Feb 2023 23:08:26 +0000 [thread overview]
Message-ID: <Y+LZ6hsjn2ZPN6tu@localhost> (raw)
In-Reply-To: <Y+BVKEUwwV2Dya+t@localhost>
On Mon, Feb 06, 2023 at 01:17:29AM +0000, Bjarni Ingi Gislason wrote:
[...]
>
> FAIL: test-c-stack2.sh
> ======================
>
> FAIL test-c-stack2.sh (exit status: 1)
>
> FAIL: test-localeconv
> =====================
>
> ../../gnulib-tests/test-localeconv.c:53: assertion 'l->frac_digits == CHAR_MAX' failed
> FAIL test-localeconv (exit status: 134)
>
l->frac_digits is 127 and CHAR_MAX is 255.
This is due to the CFLAG "-funsigned-char", which I always use having
compiled "less", which produced a lot of warnings without this flag.
The other two "FAIL" and opcode issues are still there.
[...]
next prev parent reply other threads:[~2023-02-07 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 1:17 FAIL in diffutils/gnulib-tests Bjarni Ingi Gislason
2023-02-06 1:28 ` Bruno Haible
2023-02-06 3:19 ` Bjarni Ingi Gislason
2023-02-06 18:28 ` Bruno Haible
2023-02-07 23:08 ` Bjarni Ingi Gislason [this message]
2023-02-08 0:21 ` -funsigned-char Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+LZ6hsjn2ZPN6tu@localhost \
--to=bjarniig@simnet.is \
--cc=bug-gnulib@gnu.org \
/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).