From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4] Use a proper C tokenizer to implement the obsolete typedefs test.
Date: Wed, 13 Mar 2019 22:16:43 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1903132209520.10481@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAKCAbMgpLn-GKiP91DMyDkZ8inxe+DjzDrnUwK2=+5crcYxnGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
I'm seeing failures from build-many-glibcs.py for
resource/check-obsolete-constructs:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 3198: ordinal not in range(128)
This is with LC_ALL=C (and bits/resource.h headers containing UTF-8 µ in a
comment). Code opening text files that might not be pure ASCII needs to
specify an encoding explicitly to avoid depending on the locale tests are
run with. There is also a case that the encoding specified should be
ASCII - that installed headers should be required to be pure ASCII so they
can be included in source files with any ASCII-compatible character set if
compiling with -finput-charset= (which affects included headers as well as
the main source file, so compiling "#include <sys/resource.h>" with
-finput-charset=ascii currently fails).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-03-13 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 14:59 [PATCH v4] Use a proper C tokenizer to implement the obsolete typedefs test Zack Weinberg
2019-03-11 18:57 ` Carlos O'Donell
2019-03-12 0:59 ` Zack Weinberg
2019-03-12 3:47 ` Carlos O'Donell
2019-03-13 13:47 ` Zack Weinberg
2019-03-13 22:16 ` Joseph Myers [this message]
2019-03-14 13:00 ` Carlos O'Donell
2019-03-14 13:21 ` Zack Weinberg
2019-03-14 18:06 ` Joseph Myers
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1903132209520.10481@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).