Hi Regina, On Tue, May 19, 2026 at 6:54 PM Regina Henschel <[email protected]> wrote: > Christian Lohmaier schrieb am 19.05.2026 um 16:55: > > Hi Regina, > [..] > > Can you confirm that it is indeed using the fallback path in > > configure.ac by e.g. adding a AC_MSG_ERROR([In the fallback block]) > > line to configure.ac around line 4520 after > > if test -z "$UCRTSDKDIR"; then > > > > and/or a AC_MSG_WARN([UCRTSDKDIR: $UCRTSDKDIR – UCRTSDKDIR_unix: > > $UCRTSDKDIR_unix]) after those are assigned? > > Optionally also the result of "$(win_get_env_from_vsdevcmdbat > > UniversalCRTSdkDir)" that is used in the fallback block. > > I have put a > AC_MSG_WARN([UCRTSDKDIR_1: $UCRTSDKDIR – UCRTSDKDIR_unix:$UCRTSDKDIR_unix]) > before line > reg_get_value_32 "HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft > > and a > AC_MSG_WARN([UCRTSDKDIR_2: $UCRTSDKDIR – UCRTSDKDIR_unix:$UCRTSDKDIR_unix]) > before line > dnl Hack needed at least by tml: > > In the config.log I only see > configure:14483: WARNING: UCRTSDKDIR_1: C:/PROGRA~2/WI3CF2~1/10 – > UCRTSDKDIR_unix:/mnt/c/PROGRA~2/WI3CF2~1/10/ > > There is no warning printed with UCRTSDKDIR_2.
Interesting, so my assumption was wrong and it gets the path from the registry, but for some reason on your system (and the system from the user on IRC) there's a difference in the native part - the unix part retaining the trailing slash means the value from registry does still contain the trailing slash, but that there's a difference in the PathFormat function - for the wsl-as-helper case it runs wslpath -m on the unix-style path - so as a final confirmation step, could you please try (from within the wsl-distro) wslpath -m /mnt/c/Users and wslpath -m /mnt/c/Users/ The expectation/what is the case on my system is that the first one returns C:/Users and the second one C:/Users/ – in other words it retains the slash. If there's a difference, then also please the output of wsl.exe --version ciao Christian
