bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Tim Ruehsen <tim.ruehsen@gmx.de>
Subject: Re: u8_strconv_to_locale() misbehaves on OSX (Travis CI runner)
Date: Fri, 23 Feb 2024 19:52:32 +0100	[thread overview]
Message-ID: <4751481.usQuhbGJ8B@nimes> (raw)
In-Reply-To: <1518117722.2515.13.camel@gmx.de>

Tim Ruehsen wrote on 2018-02-08
in <https://lists.gnu.org/archive/html/bug-gnulib/2018-02/msg00044.html>:
> my direct call to locale_charset() is from gnulib.
> 
> So my build correctly says UTF-8, but the homwbrew libunistring has
> been built on some unknown (OSX ?) system with their own version of 
> locale_charset() returning ASCII.

That's clearly bogus. But I can't debug builds from distros that each
have their own idiosyncratic build system.

Bruno





      reply	other threads:[~2024-02-23 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 15:59 u8_strconv_to_locale() misbehaves on OSX (Travis CI runner) Tim Rühsen
2018-02-08 17:05 ` Bruno Haible
2018-02-08 19:22   ` Tim Ruehsen
2024-02-23 18:52     ` Bruno Haible [this message]

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=4751481.usQuhbGJ8B@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=tim.ruehsen@gmx.de \
    /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).