git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Philippe Blain <philippe.blain@me.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	"Eric Sunshine" <sunshine@sunshineco.com>,
	"Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: Git 2.26.2 and failed self tests on OS X
Date: Thu, 7 May 2020 00:12:04 -0400	[thread overview]
Message-ID: <CAH8yC8maYWBGgNHX8AAwVNe+dxEwpD6yXPaFd822wPmAGaUPCA@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8nZSWSHzMiY+L4kC8OSZu9GV6H82SyvSAOqw0zX6J4xbQ@mail.gmail.com>

On Wed, May 6, 2020 at 4:36 PM Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Tue, May 5, 2020 at 8:26 AM Philippe Blain <philippe.blain@me.com> wrote:
> >  ...
> > > I am not an iconv expert - and don't intend to become one.
> > > The UTF-8-MAC conversion does probably only exist in the
> > > code for iconv shipped on Mac OS - so it could happen that this
> > > code is not open source.
> >
> > Yes, this encoding only exists in the Apple fork of iconv,
> > which is open-source (probably because of the original
> > license); tarballs can be found at [2]. However in typical Apple fashion
> > the versioning of their iconv fork is kind of undecipherable and hard to relate to the
> > upstream iconv versioning.
> >
> > Also, I searched the iconv mailing list [3] when I came across this error and the consensus
> > seemed to be that they do not intend to add this encoding upstream.
> >
> > [1] https://github.com/conda-forge/git-feedstock/issues/50
> > [2] https://opensource.apple.com/tarballs/libiconv/
> > [3] https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=utf-8-mac&submit=Search%21&idxname=bug-gnu-libiconv&max=20&result=normal&sort=score
>
> Thanks Phillipe.
>
> I found two sources for libiconv with UTF-8-Mac. First is a GitHub at
> https://github.com/fumiyas/libiconv-utf8mac. The second is the
> opensource.apple.com link you provided at [2].
>
> The GitHub claims to be layered on top of libiconv 1.16, but I was not
> able to get a working tarball from it. It looks like Apple's
> libiconv-59.tar.gz is the answer to this problem.

I had to punt on Apple's port. libiconv-59.tar.gz is libiconv-1.11. It
is too old to be useful.

libiconv-utf8mac is based on libiconv-1.16 and worked fine. It took my
patches after I figured out the complete procedure. On the upside,
libiconv-utf8mac works on Linux and Solaris too. So there is support
for UTF-8-Mac if needed.

Jeff

  reply	other threads:[~2020-05-07  4:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  7:03 Git 2.26.2 and failed self tests on OS X Jeffrey Walton
2020-05-04 15:39 ` Eric Sunshine
2020-05-04 16:52 ` Carlo Marcelo Arenas Belón
2020-05-04 17:18   ` Eric Sunshine
2020-05-04 19:08     ` Torsten Bögershausen
2020-05-04 19:19       ` Eric Sunshine
2020-05-04 19:20       ` Jeffrey Walton
2020-05-04 20:19         ` Torsten Bögershausen
2020-05-04 20:30           ` Jeffrey Walton
2020-05-04 21:39             ` Jeffrey Walton
2020-05-05  4:10               ` Torsten Bögershausen
2020-05-05 12:26                 ` Philippe Blain
2020-05-06 20:36                   ` Jeffrey Walton
2020-05-07  4:12                     ` Jeffrey Walton [this message]
2020-05-06 20:48                 ` Jeffrey Walton

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=CAH8yC8maYWBGgNHX8AAwVNe+dxEwpD6yXPaFd822wPmAGaUPCA@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=philippe.blain@me.com \
    --cc=sunshine@sunshineco.com \
    --cc=tboegi@web.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 NNTP newsgroup(s).