Re: Git 2.26.2 and failed self tests on OS X

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 5, 2020 at 8:26 AM Philippe Blain <philippe.blain@xxxxxx> 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.
>
> Cheers,
>
> Philippe.
>
> [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.

Thanks again for the help.

Jeff



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux