I was following the instruction from article https://github.com/thoughtbot/capybara-webkit/wiki/Installing-Qt-and-compiling-capybara-webkit for setting up an environment in my research of web automation. I'm using Windows installation case. Everything was perfect untill the point 11. When I type bundle exec rake build in my cmd I recieve this:
Command 'qmake CONFIG+\=test' not available.
I've read difficulties are not something unexpected at this step, so may be someone have seen this message before?
Related
I've checked the other questions and this case doesn't seem to be covered. I'm running Ubuntu in WSL on my windows machine and I'm trying to run GNATStudio, any time I attempt to run the program either via Alire or by calling it I receive the following error.
error while loading shared libraries: libxcb-shm.so.0: cannot open shared object file: No such file or directory
I've already done the basics, and verified I have the correct file installed. Calling apt-file find produces the following.
root#DESKTOP-F319G5G:/opt# apt-file find libxcb-shm.so.0
libxcb-shm0: /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0
libxcb-shm0: /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0.0.0
I've confirmed the location is in my path, as well and have restarted a few times. I'm really not too sure what my next steps should be. Any help is much appreciated!
The comment by #Bib solves this question: "install the libxcb-shm0-dev package."
I installed Scilab 5.5.2 on Windows 10, and then installed the Scilab Code Generator toolbox.
However, when I start Scilab, the following message appears and I can't use the toolbox. This problem occurs for every toolbox.
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
atomsLoad: An error occurred while loading 'xcos_code_generator-0.9.20190122':
File "C:\Users\光\AppData\Roaming\Scilab\SCILAB~1.2\atoms\x64\XCOS_C~1\09E129~1.201\macros\names" does not exist or read access denied.
(光 is my username.)
I suppose the problem comes from "\Scilab\SCILAB~1.2" in the middle of the file path. In my computer, the only folder in "Scilab" is "scilab-5.5.2", so indeed the software cannot find the file it's looking for.
Does anyone have any ideas?
I need to use the toolbox at work soon, so any help is greatly appreciated. Thank you in advance.
Note: I'm not using the latest Scilab 6.0.2 because it fails to work on my computer. It closes immediately after I open it.
I solved the problem by myself.
It was my user name "光" that caused the problem. I found people saying that user names in full-width characters such as Japanese sometimes cause problems like this.
The solution is to create another user account with a name in half-width characters and install Scilab in that account. (Just changing the full-width user name doesn't work because it doesn't change the filenames that already exist.)
I couldn't find the solution until today because I was searching for solutions only in the context of Scilab, not in the context of software in general.
I hope this answer helps someone.
I'm not sure why you are using an outdated version of Scilab. The latest version is 6.0.2 on Windows. If the newer version doesn't work properly then that's the problem you need to fix first. To test your Scilab installation you may run it in the terminal. Find the installation folder. For me, it is C:\Program Files\scilab-6.0.2\bin the on cmd go to the path and run Scilex.exe. If not uninstall everything and install it in a proper way. My recommendation is to uninstall the old Scilab you already have. Then:
Install Chocolatey package manager
Open PowerShell as Admin and run choco update all -y, once in a while update your packages this way.
run choco install Scilab -y
then open the Scilab software
run the atomsInstall("xcos_code_generator") in the console
runt the atomsLoad("xcos_code_generator") to make sure your package is installed properly. You should see this as a result:
--> atomsInstall("xcos_code_generator")
Scanning repository http://atoms.scilab.org/6.0 ... Done
ans =
!xcos_code_generator 0.9.201901 user SCIHOME\atoms\x64\xcos_code_generator\0.9.201901 I !
--> atomsLoad("xcos_code_generator");
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
Load help
Load demos
I'm trying to install the development version of the R library ranger from RStudio on Windows 7 with the command:
devtools::install_github("imbs-hl/ranger")
When I try this, I first get a pop-up with the header "make.exe - Application Error" and the message "The application was unable to start correctly (0xc000007b)."
I then get a message saying that I need to install additional build tools. This downloads RTools. I then get an identical pop up like the make.exe one, except that this time it's for sh.exe. After I click ok, it then does a somewhat long install of RTools. The setup window closes and the development packages remain uninstalled.
Note: when I run either sh.exe or make.exe from the windows command line, I get the same errors. This might have something to do with the fact that I have cygwin installed.
I can get sh.exe and make.exe to run from the windows command line if I remove RTools from the path, leaving only cygwin. However, this doesn't change the problem I get when I try installing the development version of ranger.
Any help would be appreciated.
I am aware one question exists already but he had a different issue as he answered himself. I am running on windows 32 bit and trying to run heroku. It stopped somehow after I restart the terminal one time. Now literally anything I enter using the heroku cli, I get this error:
'ENOENT': spawn tasklist ENOENT
I tried running heroku version but still the same. In my path I have linked it to C:\. . .\Heroku\bin. It worked but even after reinstalling it does not work.
P.S. Does this have anything to do with my node installation? I have node installed too. Is it clashing?
On Windows, you need to locate tasklist.exe on your PC.
Typically, it is found in Windows/system32/
If it is there, put the basepath to it in PATH Environmental variable.
Then open new cmd.exe as Administrator.
Now, you should NOT see the 'ENOENT': spawn tasklist ENOENT error message.
I had the same issue, while I was not operating as Administrator. When running heroku commands as admin in shell, it started working. I found this discussion to be helpful: https://github.com/heroku/heroku-pg-extras/issues/129.
Hope that helps.
Cheers
I also had same issues but i resolved mine by running cmd as adminstrator. and login back into heroku by using these command
heroku auth:login
and wala! you can bounce back to your project.
i recommend looking at these
helpful link
A bit frustrated right now. I have an R project that I built several weeks ago that I have not touched in those weeks. Come back to R Studio to do some debugging, and it will not rebuild the package. When I run the Check command from within the RStudio UI, the error I get is:
Error: Check failed: 'P:\MosaicPA\R Packages/Mosaic.VoronoiV2.Rcheck' doesn't exist
Execution halted
Exited with status 1.
When I try the Install and Restart option, I get this error:
==> Rcmd.exe INSTALL --no-multiarch --with-keep.source Mosaic.VoronoiV2
Warning: invalid package 'Mosaic.VoronoiV2'
Error: ERROR: no packages specified
Exited with status 1.
I have not seen these messages before, and cannot figure out what I am doing wrong, since nothing has changed.
I am not new to programming, but I am new-ish to the R environment. Cannot figure out what has changed, and I dont know what the .Rcheck file is, and I dont know why R doesnt create it. None of my other projects have a .Rcheck file or directory, and I dont know if this is supposed to be a file or directory. I have tried creating the project from scratch. Same issue.
Using R 3.4.1 and the latest R Studio version.
Well, Windows permissions strikes again...personally, I find Windows to be a HUGE POS because of stuff like this. Problem resolved after I reinstalled R under my domain account...I was suspicious of this, but couldn't find a way to confirm. Just reinstalled R and it worked. What I really wish is that when it IS a permissions problem, that Windows would report it as such, so the software can tell the end user this, vs sending us down some rabbit hole, chasing some non-existent problem, which happens too much as it is. Thanks, Redmond! But...I understand...after all, MS is too busy working on the next emoji standard...which is a priority, so who has time to make the OS better. End of rant.