windows-subsystem-for-linux

GNU Fortran compiler on Windows Subsystem for Linux - Segmentation fault with passing internal function to another procedure [duplicate]

北城以北 提交于 2020-12-12 05:11:31
问题 This question already has an answer here : Segmentation fault when passing internal function as argument (1 answer) Closed 11 days ago . I believe the following is a valid Fortran 2008 program and it works fine on genuine macOS, Linux, and Windows operating systems with both Intel and GNU Fortran compilers. module InternalFuncCaller_mod implicit none abstract interface function getInternalFunc_proc(input) result(output) implicit none real, intent(in) :: input real :: output end function

GNU Fortran compiler on Windows Subsystem for Linux - Segmentation fault with passing internal function to another procedure [duplicate]

一世执手 提交于 2020-12-12 05:10:48
问题 This question already has an answer here : Segmentation fault when passing internal function as argument (1 answer) Closed 11 days ago . I believe the following is a valid Fortran 2008 program and it works fine on genuine macOS, Linux, and Windows operating systems with both Intel and GNU Fortran compilers. module InternalFuncCaller_mod implicit none abstract interface function getInternalFunc_proc(input) result(output) implicit none real, intent(in) :: input real :: output end function

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-aadithyasb'

自闭症网瘾萝莉.ら 提交于 2020-12-08 15:51:08
问题 I am using WSL in Windows 10. I have this warning getting displayed when I run a python file: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-aadithyasb' I can understand that the XDG_RUNTIME_DIR environment variable is not set and it is creating its own path /tmp/runtime-aadithyasb I am getting this warning from the moment I installed Xserver for Windows using VcXsrv to open plots when the file is ran. Wy question is should I add this XDG_RUNTIME_DIR environment variable

Unable to get PhpStorm to connect to Xdebug running in WSL 2

依然范特西╮ 提交于 2020-12-07 15:21:55
问题 I am having trouble getting PhpStorm 2020.2 to work with xdebug with the following setup: WSL2 running Ubuntu 20, with PHP and php-xdebug installed. Whenever I run my tests with debugging enabled it says "Connection was not established.". This is what the Xdebug log shows: [5877] Log opened at 2020-08-14 17:20:45 [5877] I: Connecting to configured address/port: 172.18.48.1:9006. [5877] E: Time-out connecting to client (Waited: 200 ms). :-( [5877] Log closed at 2020-08-14 17:20:46 This is for

Unable to get PhpStorm to connect to Xdebug running in WSL 2

泪湿孤枕 提交于 2020-12-07 15:18:34
问题 I am having trouble getting PhpStorm 2020.2 to work with xdebug with the following setup: WSL2 running Ubuntu 20, with PHP and php-xdebug installed. Whenever I run my tests with debugging enabled it says "Connection was not established.". This is what the Xdebug log shows: [5877] Log opened at 2020-08-14 17:20:45 [5877] I: Connecting to configured address/port: 172.18.48.1:9006. [5877] E: Time-out connecting to client (Waited: 200 ms). :-( [5877] Log closed at 2020-08-14 17:20:46 This is for

Unable to get PhpStorm to connect to Xdebug running in WSL 2

和自甴很熟 提交于 2020-12-07 15:18:13
问题 I am having trouble getting PhpStorm 2020.2 to work with xdebug with the following setup: WSL2 running Ubuntu 20, with PHP and php-xdebug installed. Whenever I run my tests with debugging enabled it says "Connection was not established.". This is what the Xdebug log shows: [5877] Log opened at 2020-08-14 17:20:45 [5877] I: Connecting to configured address/port: 172.18.48.1:9006. [5877] E: Time-out connecting to client (Waited: 200 ms). :-( [5877] Log closed at 2020-08-14 17:20:46 This is for

No internet connection on WSL Ubuntu (Windows Subsystem for Linux)

只谈情不闲聊 提交于 2020-12-01 07:47:36
问题 Recently I installed WSL Ubuntu 18.04 on my Windows machine, but nothing seems to work properly, because I have no internet access . I tried a few commands and sudo apt update says 'Connection failed' and ping google.com literally takes foreveras you can see in this screenshot: https://i.stack.imgur.com/NXJNx.png I also checked nano /etc/resolv.conf and made sure that the nameservers are right, completely disabled Kaspersky and its firewall, disabled Hyper-V, reinstalled WSL a few times and