On Mon, May 4, 2020 at 4:19 PM Torsten Bögershausen <tboegi@xxxxxx> wrote: > On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote: > > ... > > > Does > > > ./t3902-quoted.sh -v -d > > > give anything useful ? > > > > Yes, it looks like the command reveals a couple of problems. > > > > I'll have to look into my iconv recipe. It has not changed in a while, > > so something else may be responsible for the failure. > > https://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh. > > > > I'm not sure what to do with the HEAD problems. > > > > $ ./t3902-quoted.sh -v -d > > Initialized empty Git repository in > > /Users/jwalton/Build-Scripts/git-2.26.2/t/trash > > directory.t3902-quoted/.git/ > > expecting success of 3902.1 'setup': > > > > mkdir "$FN" && > > for_each_name "echo initial >\"\$name\"" && > > git add . && > > git commit -q -m Initial && > > > > for_each_name "echo second >\"\$name\"" && > > git commit -a -m Second && > > > > for_each_name "echo modified >\"\$name\"" > > > > > > fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed: > > precomposed unicode is not supported. > > If you want to use decomposed unicode, run > > "git config core.precomposeunicode false" > > > > I am quite sure, that the trouble starts here. > It seems as if you are building iconv yourself ? > And that iconv does not include "UTF-8-MAC", which is a speciality > for Mac. Oh, thanks. I was not aware. I'll open a bug report with the iconv folks letting them know configure has some gaps on OS X. > Are there any special reasons to build your own iconv ? Yes, iconv bugs on older platforms. The only way I've found to avoid intermittent problems on older platforms is using the latest iconv (which is pretty stable nowadays), and avoid the glibc iconv. Jeff
