After running 'msfconsole', I see this error. Help me, please
CANNOT LINK EXECUTABLE "ruby": library "/data/data/com.termux/files/usr/lib/ruby/2.7.0/aarch64-linux-android/bigdecimal.so" not found: needed by main executable
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 am trying to get a program running. I installed grpc-java in one of my folders on linux. I did ../gradlew publishToMavenLocal for grpc-java and it was successful but I don't find anything generated in /usr/local. How to resolve the compile error below and make sure java-plugin is found? Any pointers? I am new to linux.
compiling route
/usr/local/grpc/java-plugin-1.15.0/exe/java_plugin/protoc-gen-grpc-java: program not found or is not executable
--grpc-java_out: protoc-gen-grpc-java: Plugin failed with status code 1.
grpc is not executable binary (it is a library). anyways, the output of publishToMavenLocal should be in ~/.m2/ directory if you haven't override default.
if you want to compile grpc, please read COMPILING.md.
i recommend to follow https://grpc.io/docs/quickstart/java/
I wrote a simple code to test CUDA with Qt on Linux Ubuntu.
While running app within Qt IDE I get the following error:
However while running app from command line I don't get any erorr and all computation done by CUDA are correct.
Also while running CUDA samples from command line, everything is okay.
Also all paths in Qt .pro file are set correctly
So the question is why Qt IDE prompts me with above error?
Ok, problem fixed.
Turns out that LD_LIBRARY_PATH does not do its job.
What I did instead was:
add this
/usr/local/cuda-7.0/lib64
to
/etc/ld/so/conf
file
Run
sudo ldconfig
I hope it will help somone
When I use this plugin, Grunt for Brackets, it doesn't seem to work for me. I've looked and looked and looked through the files of the extension, and when I "grunt," my devtools spit out this log.
[node-log 10:01:49 AM] { '0': { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn' } }
I'm not exactly sure what that means...
Here is a link to the extension.
The author has not updated anything in months, and there is an open issue ticket, however there hasn't been any responses.
If someone could help me decipher this log, I would greatly appreciate it.
Do you have Grunt installed on your computer already? If so, is it installed in the standard location? (e.g. did you intsall using npm -g grunt?)
ENOENT basically means "file not found," and since the error message also says spawn I'm guessing the problem is it's unable to find the Grunt binary to execute.
Update: Looks like a bug in how the current version of the extension was packaged. You should be able to fix it yourself this way:
Help > Show Extensions Folder in Brackets and find the brackets-grunt extension in the 'user' subfolder
Open a command prompt at that location
cd into the node folder inside the extension
Run npm install
I added a note to the bug, so hopefully the extension's author will fix it soon too.