winest

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Unable to connect to WSL on Windows 10 1903 build #25127
    winest
    Participant

    Hi, it’s a very simple ini file. So you can extract config by the following command:

    C:\Windows\System32\bash.exe -c “awk -F = ‘/^root/ {gsub(/^[ \t]/, \”\”, \$2); print \$2}’ /etc/wsl.conf”

     

    Thanks

    in reply to: Unable to connect to WSL on Windows 10 1903 build #25122
    winest
    Participant

    Hi, I guess I know the problem. The root cause is VisualGDB assume Windows drives are mounted at default path (/mnt/c/VisualGDB, for example) while some people like me will change mounting path to other places(/c/VisualGDB, for example) based on the suggestion from https://devblogs.microsoft.com/commandline/automatically-configuring-wsl/

    Hope VisualGDB can implement the fix which read the setting from /etc/wsl.conf

    BTW, another error was output saying that “Loading machine index from C:\Users\winest\.vagrant.d\data\machine-index\index…
    failed to load vagrant VM list: Could not find a part of the path “.

    I don’t know whether it will affect anything or it’s just a warning.

    Thanks

     

     

    Key error:

    C:\Users\winest>C:\WINDOWS\system32\bash.exe -c “gcc -std=gnu99 \”/mnt/e/VisualGDB/TargetTools/LinuxAppLauncher.c\” -o /tmp/LinuxAppLauncher-v2 -lutil”
    gcc: error: /mnt/e/VisualGDB/TargetTools/LinuxAppLauncher.c: No such file or directory
    at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass2_2`1.<RunAction>b__0()

     

    Full log:

    Initializing assemblies: 14 msec
    Registering factories: 117 msec
    Initializing VisualGDB 5.4.106.3193
    Checking fonts/colors: 73 msec
    Level 2 initialization: 732 msec
    Loading machine index from C:\Users\winest\.vagrant.d\data\machine-index\index…
    failed to load vagrant VM list: Could not find a part of the path ‘C:\Users\winest\.vagrant.d\data\machine-index\index’.
    —————— System.IO.DirectoryNotFoundException ——————
    System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:\Users\winest\.vagrant.d\data\machine-index\index’.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
    at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
    at System.IO.File.ReadAllText(String path)
    at hy1.e()
    at hy1.m()
    Loading Linux toolchain list for winest@localhost:50022 (SSH)
    Creating toolchain controller: initial selection (registry)
    SelectToolchainByKey(com.sysprogs.toolchain.default-gcc )
    Loading Linux toolchain list for (Windows 10 Linux subsystem)
    Creating toolchain controller: initial selection (registry)
    SelectToolchainByKey(com.sysprogs.toolchain.default-gcc )
    Committing LinuxTargetPage…
    Testing project settings…
    Running toolchain tester…
    C:\WINDOWS\system32\bash.exe -c “gcc -std=gnu99 \”/mnt/e/VisualGDB/TargetTools/LinuxAppLauncher.c\” -o /tmp/LinuxAppLauncher-v2 -lutil”
    Unexpected exception: Failed to build Linux subsystem launcher. Please check that the Linux subsystem is installed and contains gcc.
    —————— System.Exception ——————
    System.Exception: Failed to build Linux subsystem launcher. Please check that the Linux subsystem is installed and contains gcc.
    at wr.q.i1()
    at wr.q.n(CommandLineAction b, CommandFlags c, Boolean a)
    at wr.q..ctor(CommandLineAction d, CommandFlags b, y42 a, Boolean c)
    at wr.g_2(y42 f, String e, String c, String a, ExpandedEnvironment b, CommandFlags d)
    at hi2.m2(Int32& a, String b, String h, String c, ModifiedEnvirionment e, Int32 g, Boolean i, CommandFlags d, co2 f)
    at hi2.k2(String b, String e, String f, ModifiedEnvirionment a, Int32 d, Boolean c)
    at va2.r(du a)

     

     

    in reply to: Unable to connect to WSL on Windows 10 1903 build #25107
    winest
    Participant

    Of course I have already installed all development tools and is able to build my c++ projects by using ssh.

     

    Output of “gcc -v”:

    Using built-in specs.COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
    Target: x86_64-linux-gnu
    Configured with: ../src/configure -v –with-pkgversion=’Ubuntu 5.5.0-12ubuntu1′ –with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs –enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ –prefix=/usr –program-suffix=-5 –enable-shared –enable-linker-build-id –libexecdir=/usr/lib –without-included-gettext –enable-threads=posix –libdir=/usr/lib –enable-nls –with-sysroot=/ –enable-clocale=gnu –enable-libstdcxx-debug –enable-libstdcxx-time=yes –with-default-libstdcxx-abi=new –enable-gnu-unique-object –disable-vtable-verify –enable-libmpx –enable-plugin –enable-default-pie –with-system-zlib –enable-objc-gc –enable-multiarch –disable-werror –with-arch-32=i686 –with-abi=m64 –with-multilib-list=m32,m64,mx32 –enable-multilib –with-tune=generic –enable-checking=release –build=x86_64-linux-gnu –host=x86_64-linux-gnu –target=x86_64-linux-gnu
    Thread model: posix
    gcc version 5.5.0 20171010 (Ubuntu 5.5.0-12ubuntu1)

Viewing 3 posts - 1 through 3 (of 3 total)