How can I build the drivers for MariaDB for PyQt? I did follow the instructions here https://doc.qt.io/qtforpython/overviews/sql-driver.html
But I stuck on these steps
mkdir build-sqldrivers
cd build-sqldrivers
. In which directory should I type these commands? Inside somewhere? I executed them just in C:\ dir. Is this a problem?
Related
I am a complete newbie to Linux and trying to open an AppImage called Magick which is an Imagemagick application.
I tried right clicking on the AppImage and checked "run file as an executable" option but that didn't work. Another thing that I tried is running this command,
chmod a+x magick.AppImage
This gives me an error,
chmod: cannot access 'magick.AppImage': No such file or directory
I have also tried running the file by navigating into the folder that contains the file and opening up the terminal there but still no luck.
I am running Ubuntu on Oracle VM VirtualBox.
ImageMagick is a command-line tool, you don't run it by clicking on it.
To run it in a terminal you need to
Set the executable flag on the .AppImage (once for all): chmod +x TheApp.AppImage
Then to run it just invoke the AppImage: ./TheApp.AppImage <arg1> <arg2> ....
If the directory with your .AppImage is in your PATH, you can remove the ./ (or whatever directory the AppImage is in).
ImageMagick is also available as a regular application from your Ubuntu repository: sudo apt install imagemagick
Trying to install Cytoscape program on linux cytoscape. And I don't know how because first install button transfers me to HTML page and nothing is downloadable. (I have java installed). I tried to download tar.gz file but I am stuck, because there is no configure file and it says I have no permission for it. What should I do?
Once java 11 is installed on your computer try this:
ctrl+alt+T #open Ubuntu's console
cd /home/fulanita/Downloads #this is the directory where my computer has cytoscape.
chmod +x ./Cytoscape_3_8_1_unix.sh
./Cytoscape_3_8_1_unix.sh #3.8.1 is the last version for Ubuntu
the program will start to install
If anyone comes here in search for an answer I found a solution.
You go to you directory where you keep extracted tar.gz
with cd -Folderdestination/ you locate a folderwhere you keep a file named cytoscape.sh, and with command
sudo sh cytoscape.sh
install the program.
I'm running Cygwin 64bit but can't seem to get OpenShift oc command line to work
I downloaded oc.tar.gz ( from here https://mirror.openshift.com/pub/openshift-v3/clients/3.6.173.0.5/linux/oc.tar.gz ), unzipped it and placed it in my path in /usr/bin
When I try to run: oc login I get the following.
-bash: /usr/bin/oc: cannot execute binary file: Exec format error
Do I need to somehow 'install' the executable ?
Any help would be much appreciated.
In addition to #Graham Dumpleton's answer:
open cygwin and check for directory /usr/local/bin
mkdir -p local/bin
$ cd /usr/local/bin
if it does not exists:
$ mkdir -p local/bin
finally extract the windows package:
$ cp /cygdrive/c/Users/me/Downloads/oc-3.5.5.31.24-windows.zip /usr/local/bin/
unzip oc-3.5.5.31.24-windows.zip
$ oc version
oc v3.5.5.31.24
kubernetes v1.5.2+43a9be4
features: Basic-Auth
Use the Windows binary from the following page:
https://github.com/openshift/origin/releases
From project homepage
https://www.cygwin.com/
Cygwin is not:
a way to run native Linux apps on Windows. You must rebuild your
application from source if you want it to run on Windows.
a way to magically make native Windows apps aware of UNIX®
functionality like signals, ptys, etc. Again, you need to build your
apps from source if you want to take advantage of Cygwin
functionality.
I am new to Go, and I have a docker plugin written in Go on my MAC. I build it with the following command:
env GOOS=linux GOARCH=amd64 go build
The output is binary file. When I copy it to CoreOS and try to execute:
./my-binary-file
the result is:
"2016/12/07 08:05:00 Error Group root not found"
The OS on which file is executed is CoreOS. I've checked MAC and CoreOS, both of them are x86_64.
Why then I get this error?
EDIT:
The problem was in ServerUnixGroup. It should be "docker" instead of "root".
The problem was in ServerUnixGroup. It should be "docker" instead of "root". – user2739823
I have Jenkins set up on a machine with the NodeJS plugin. Sadly, whenever I try to use the plugin in a build, it fails with:
[workspace] $ node /tmp/hudson3477900862350780409.js
FATAL: command execution failed
java.io.IOException: Cannot run program "node" (in directory
"/var/lib/jenkins/jobs/XXX/workspace"): error=2, No such file or directory
When I log into the machine as the jenkins user, I can use node through command line. I also added the path to node (/opt/node-0.6.18/bin) into the Configuration screen for the current working node (which is only one: master).
I've been stuck with this for a while, any help would be highly appreciated.
Cheers!
Well, this isn't the most elegant of solutions, but it worked: I simply made a symlink to from /bin/ to the installation path for node and now the problem's gone.
ah easy, you need to tick "Provide Node/npm bin folder to PATH" when running a "execute shell" build task"
I am using NVM and I had the same issue. One workaround was to create a symlink:
ln -s /root/.nvm/versions/node/v8.11.3/bin/node /bin/node
ln -s /root/.nvm/versions/node/v8.11.3/bin/npm /bin/npm
For Jenkins running in Docker, use jenkins/jenkins:latest image to avoid this issue.
the error came up just because you did't install node in your machine.after you installed it,and add it to PATH,then the problem can be solved.
hope it helps.