Hi Kiyoshi, > Le 6 juil. 2020 à 08:51, Kiyoshi KANAZAWA <yoi_no_myou...@yahoo.co.jp> a > écrit : > > Hi, Akim. > > with /usr/xpg4/bin/sh: > $ $coreutilsbin/printf '\u2022\n' > ?
> I have probles with coreutils's cp, mv and ln, so they are disabed such as > $ /usr/xpg4/bin/mv $coreutilsbin/cp $coreutilsbin/cp- > $ /usr/xpg4/bin/mv $coreutilsbin/mv $coreutilsbin/mv- > $ /usr/xpg4/bin/mv $coreutilsbin/ln $coreutilsbin/ln- > > Doing the same thing to coreutils's printf such as > $ /usr/xpg4/bin/mv $coreutilsbin/printf $coreutilsbin/printf- > now, /usr/bin/printf comes to the default printf. > > With this condition, tried bison-3.6.90 again, but have the same failure > numbers. > $ ./configure --prefix=/opt/local SHELL=/opt/local/bin/bash --disable-nls > --without-libtextstyle-prefix --with-libreadline-prefix=/opt/local CC=gcc I was unclear: Bison does not use the coreutils in anyway. However, it uses the same gnulib component to print the bullet as the coreutils' printf to handle unicode escapes. That helps us having a reproducible test case. Bison uses '.' as fallback, but printf should print '\u2022' (six characters) as fallback. So in both cases it failed. We could imagine '?' is the way your terminal rendered something it failed to display, but it's unlikely, given that the log of the tests you sent could not have been transformed by the terminal. But just in case, what does $ $coreutilsbin/printf '\u2022\n' | od -t x1 give? I have: $ printf '\u2022\n' | od -t x1 0000000 e2 80 a2 0a 0000004 Cheers!
