CMake Progress Marks Displayed Garbled After Latest pacman -Syu
Description
After the latest pacman update for the system, the cmake progress marks output appears garbled with duplicated characters, etc.. Almost like there is a code-page or encoding snafu. For example, after the latest updates on Win10, I see
[ 8%] Built target bs2_default_padded_checksummed_asm
Consolidate compiler generated dependencies of target elf2uf2
Consolidate compiler generated dependencies of target pioasm
[100%] Built target elf2uf2
[100%] Built target pioasm
[[ 1111%%]] NoN oi nisntsatlall ls tsetpe pf ofro r' P'iEoLaFs2mUBFu2iBludi'ld
'
[ 13[% ]1 4%]C omCpolmeptleedt e'dP i'oEaLsFm2BUuFi2lBdu'il
d'
[[ 2299%%]] BBuuiilltt ttaarrggeett EPLiFo2aUsFm2BBuuiilldd
Scanning dependencies of target pwm_led_fade
Consolidate compiler generated dependencies of target pwm_led_fade
[ 31%] Linking CXX executable pwm_led_fade.elf
[100%] Built target pwm_led_fade
All text except the progress mark info (in some instances) appears fine.
I don't know what the issue may be, but after discovering it, I thought I would pass it along.
Verification
- [X] I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)
Windows Version
Windows 10 Version 21H2 (OS Build 10944.2130)
Expected behavior
I expected all compiler and cmake output to be readable without duplicated or garbled characters.
Actual behavior
Parts of the cmake output was unreadable with garbled and duplicated characters. For example, a very large part of the cmake output is gibberish:
[ 85[% ]8 6%[B] u 8i8l%Bd]ui inlgdB iuCni glo dbCij neogcb tjA eSCcMMt a okCbeMjFaieklceetFs i/ClpMewasmk/_eplFweimd
l__elfsea/dd_pefw.amdd_ielr.e/ddCi__rf//amCds_ey/.smd6si4yr/s/o6Cp4_t///omppsityc/sop6/i4pc/iooc/popt-i/scpdoik-c/so
sd/rkpc/i/scrropc-2/s_rdcpko2/m_smcroocnm//mrpopin2c/_opc_iofcmlomo_oafntl//opfailtco/oaf_tlf_oliaontai_ttm/_afrtolh
mo..acct.._oovbb1jj_
rom_shim.S.obj
[ 89%[] 9B1u%i]l diBnugi lCd [io nb9gj2 e%Ac]St M B CuoMibaljkdeeicFntig l CeAMsSa/Mkp ewoFmbi_jlleeecsdt/_ pfCwaMm
da_ekl.eedFdii_rlf/eaCsd_/e/p.mwdsmiy_rsl/6eC4d_/_/ofmpastdy/esp.6id4ci/oro//ppCti_/c/pomi-scsyods/k6p/4is/croocp-/t
sr/dppk2i/_cscoro/cmp/mirocpno2/-_pscidockmo/m_somrnac/l/plriopcc2o/__pcmioecmmom__oomnpa/slp/limocecom.__cso.tpoasb
n_jda
aeradb_il.iSn.ko/bcjr
t0.S.obj
[ 94%] Building CXX objec[t 9C5M%a]k eFBiulielsd/ipnwgm _Cl eodb_jfeacdte .CdMiark/eCF_i/lmessy/sp6w4m/_olpetd/_pfi
acdoe/.pdiicro/-Cs_d/km/ssyrsc6/4r/po2p_tc/opmimcoon//ppiiccoo[-_ ss9dt7ka%/n]sd racrB/dur_ipll2id_nickno/gmn meCow
n_o/dbpejilececott_e s.CtcMapanpkd.eaoFrbidjl_e
sl/ipnwkm/_blienda_rfya_dien.fdoi.rc/.Co_b/jm
sys64/opt/pico/pico-sdk/src/rp2_common/pico_stdio/stdio.c.obj
[ 98%] Building C object CMakeFiles/pwm_led_fade.dir/C_/msys64/opt/pico/pico-sdk/src/rp2_common/pico_stdio_uart/stdi
o_uart.c.obj
[100%] Linking CXX executable pwm_led_fade.elf
The packages installed that were updated today before the behavior appeared were:
libnghttp2 (1.49.0-1 -> 1.50.0-1)
libffi (3.4.2-1 -> 3.4.3-1)
libgpg-error (1.45-2 -> 1.46-2)
liblzma (5.2.6-1 -> 5.2.7-1)
libsqlite (3.39.2-1 -> 3.39.4-1)
libcurl (7.85.0-1 -> 7.85.0-2)
curl (7.85.0-1 -> 7.85.0-2)
file (5.42-2 -> 5.43-1)
libexpat (2.4.8-2 -> 2.4.9-1)
libfido2 (1.11.0-1 -> 1.12.0-1)
perl-Net-SSLeay (1.90-1 -> 1.92-1)
perl-IO-Socket-SSL (2.074-1 -> 2.075-1)
git (2.37.3-1 -> 2.38.0-1)
libgnutls (3.7.7-1 -> 3.7.8-1)
libksba (1.6.0-2 -> 1.6.1-1)
mingw-w64-x86_64-libwinpthread-git (10.0.0.r72.g1dd2a4993-1 -> 10.0.0.r113.g57fd0b77a-1)
mingw-w64-x86_64-gcc-libs (12.2.0-1 -> 12.2.0-4)
mingw-w64-x86_64-aom (3.4.0-1 -> 3.5.0-1)
mingw-w64-x86_64-arm-none-eabi-binutils (2.38-1 -> 2.39-1)
mingw-w64-x86_64-expat (2.4.8-1 -> 2.4.9-1)
mingw-w64-x86_64-libffi (3.4.2-2 -> 3.4.3-1)
mingw-w64-x86_64-zlib (1.2.12-1 -> 1.2.13-1)
mingw-w64-x86_64-tcl (8.6.11-5 -> 8.6.12-1)
mingw-w64-x86_64-tk (8.6.11.1-2 -> 8.6.12-1)
mingw-w64-x86_64-xz (5.2.6-1 -> 5.2.7-1)
mingw-w64-x86_64-python (3.10.6-1 -> 3.10.8-1)
mingw-w64-x86_64-arm-none-eabi-gdb (9.2-5 -> 9.2-6)
mingw-w64-x86_64-arm-none-eabi-newlib (3.3.0-1 -> 4.2.0.20211231-2)
mingw-w64-x86_64-pkgconf (1.8.0-2 -> 1~1.8.0-2)
mingw-w64-x86_64-libuv (1.42.0-3 -> 1.44.2-1)
mingw-w64-x86_64-ninja (1.11.1-1 -> 1.11.1-2)
mingw-w64-x86_64-libxml2 (2.9.14-4 -> 2.10.2-4)
mingw-w64-x86_64-cmake (3.24.1-3 -> 3.24.2-3)
mingw-w64-x86_64-headers-git (10.0.0.r72.g1dd2a4993-1 -> 10.0.0.r113.g57fd0b77a-1)
mingw-w64-x86_64-crt-git (10.0.0.r72.g1dd2a4993-1 -> 10.0.0.r113.g57fd0b77a-1)
mingw-w64-x86_64-extra-cmake-modules (5.97.0-1 -> 5.98.0-2)
mingw-w64-x86_64-winpthreads-git (10.0.0.r72.g1dd2a4993-1 -> 10.0.0.r113.g57fd0b77a-1)
mingw-w64-x86_64-gcc (12.2.0-1 -> 12.2.0-4)
mingw-w64-x86_64-gcc-libgfortran (12.2.0-1 -> 12.2.0-4)
mingw-w64-x86_64-gcc-fortran (12.2.0-1 -> 12.2.0-4)
mingw-w64-x86_64-gdb (12.1-3 -> 12.1-4)
mingw-w64-x86_64-gdb-multiarch (12.1-3 -> 12.1-4)
mingw-w64-x86_64-libpng (1.6.37-6 -> 1.6.38-1)
mingw-w64-x86_64-libheif (1.13.0-1 -> 1.13.0-2)
xz (5.2.6-1 -> 5.2.7-1)
pinentry (1.2.0-2 -> 1.2.1-1)
pacman-contrib (1.6.0-1 -> 1.7.1-1)
rsync (3.2.3-2 -> 3.2.6-1)
tzcode (2022c-1 -> 2022d-1)
Not sure which if any are responsible.
Repro steps
On windows with the pico-SDK installed, pick any example program to compile. Create the out-of-source build dir, run cmake and then make.
Nothing more involved than that. I'm using Msys2 64 terminal, which is
mintty 3.6.1 (x86_64-pc-msys)[Windows 19044]
Are you willing to submit a PR?
I would if I had a clue which part may be involved. Can't help here.