On Tue, May 5, 2020 at 12:10 AM Torsten Bögershausen <tboegi@xxxxxx> wrote: > > On Mon, May 04, 2020 at 05:39:50PM -0400, Jeffrey Walton wrote: > > On Mon, May 4, 2020 at 4:30 PM Jeffrey Walton <noloader@xxxxxxxxx> wrote: > > > > > > ... > By the way, does > ./t3910-mac-os-precompose.sh > work on your system ? > > So far I am not aware about any problems with iconv from MacOs > being reported here on the list. > Which problems/bugs did you found in the iconv shipped with MacOs, > especially together with Git ? Thanks again Torsten . So there are several problems with libiconv. First, sometimes it is too old and carries bugs with it. For example, sed and awk fail to build and pass their self tests because they expect a minimum version of libiconv. Second, there are some modern bugs that needs fixing. They were reported after libiconv 1.16 was released. It needs patches. Third, libiconv cannot get through testing with UBsan. It causes a number of packages to fail to configure or pass their self tests. It needs patches. Fourth, libiconv cannot get through testing with Asan and Valgrind. It leaks resources like a sieve, and leaves memory and file handles open. It causes a number of packages to fail to configure or pass their self tests. It needs more patches. Due to all the problems with libiconv I just patch it and build it everywhere I need it. The other option is to wait for the maintainers to fix libiconv. Based on some reading about the UTF-8-Mac problem I don't think that will happen. And they are not interested in fixing the resource leaks. GNU has such low coding standards... Jeff
