I am using MSYS2 in Windows 10. git works fine, however gitk gives the error:
/usr/bin/gitk: line 3: exec: wish: not found
Some googling suggested this may be because TK is not installed, however I tried:
pacman -S tk
which gave the error:
error: target not found: tk
How do I get gitk to work in this environment?
Try running the 64-bit MinGW shell (one of the three environments provided by MSYS2), installing the package mingw-w64-x86_64-tk, and then running gitk.
Gitk works on my system, and wish is provided /mingw64/bin/wish.exe.
I confirm C:\prgs\git\PortableGit-2.7.0-64-bit\cmd\gitk.exe works just fine.
Make sure you are executing it from a regular CMD session or from C:\prgs\git\PortableGit-2.7.0-64-bit\git-bash.exe
I would not try and run it from a Cygwin session.
Related
I followed the Installing Bazel on Windows, and everything work but the patch. I get the following error
/usr/bin/bash: line 1: patch: command not found.
I installed msys64 in C:\dev\msys64, and added C:\dev\msys64\usr\bin to my PATH. Bazel work fine, but when I open C:\dev\msys64\usr\bin\bash.exe and I type patch, the command is not found.
If I open mingw32.exe, mingw64.exe or msys2.exe, and type "patch" it works. it is well installed. I tried to reinstall it many time. but still the bash.exe does not have the patch command.
I used the following command pacman -S zip unzip patch diffutils git. Everything seems to be well installed.
The error occurs when building the rules_go, specifically the following element wrapper
I'm trying to literally download and run the ElectronNet demo (found here). I install the CLI tool, which appears to be accomplished successfully, but when I try to use the tool, terminal does not recognize it. Shown below:
% dotnet tool install electronnet.cli -g
Tool 'electronnet.cli' is already installed.
%electronize start
zsh: command not found: electronize
What could be going on here?
I guess it's something with your path&zsh,
if you try:
~/.dotnet/tools/electronize start
is that work for you?
If so, you can fix your path by editing ~/.zshrc, add this:
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet/bin"
and source the file by running: ". ~/.zshrc"
I have tried to get vala working on Windows and it does not work, I have followed the steps on the website:
I downloaded and installed msys2
Then I ran
pacman -Syu
pacman -Su
Then I ran the command on the vala website
pacman -S mingw-w64-x86_64-gcc mingw-w64-x86_64-pkg-config mingw-w64-x86_64-vala
Then I tried to run valac and it says command not found.
Am I missing something? I tried just vala but that does not work, I tried to run the command again and it said that it was already installed and up to date.
You probably did not start "mingw64.exe" (The msys2 subsystem for mingw64-x86_64).
There are three distinct subsystems in msys2 (each also has its own pacman package repository):
msys2
mingw32
mingw64
You can launch a shell for any of them. The current best solution is to use the included launchers (msys2.exe, mingw32.exe and mingw64.exe).
See here for more documentation:
https://www.msys2.org/wiki/Launchers/
https://www.msys2.org/wiki/MSYS2-introduction/
I have compiled both castalia and omnet and everything was right but
when running simulation using command line I got this error:
/c/Castalia/Simulations/radioTest$ ../../bin/Castalia
bash: ../../bin/Castalia: /usr/bin/python: bad interpreter: Permission denied
I installed python 2.6 in usr/bin path. but still has that error.
I tried #! usr/bin/env, but again I got same error.
how i can solve this problem?
In general Castalia is not supported under Windows, and any success people have running it is based on homebrews (custom solutions based on their configuration). The more reliable solution would be to run Ubuntu (perhaps on a virtual machine in Windows). Mac OS X works fine too.
Seeing your bash tag, I am not sure how you got to run bash on Windows (Cygwin?), but if you have a bash shell you can run which python to see where python resides on your system. If it's something other than /usr/bin/python then you can try changing the shebang line to the correct location. Or you can try #!/usr/bin/env python (notice the python executable after the path).
Also make sure you have the permission to run Python as the user you are logged in! How would you run any python script from command line?
Finally it is recommended that you have Python 2.7 installed, but it may run fine with 2.6 too.
this is what I get when I use bower init
what could be the problem??
The problem is with the terminal/console you're using to.
I ran into this same problem other day, I was using Git bash as my terminal, and trying to run this command with Node.js command prompt worked normally.
Try to use another terminal, like cmder (I really recommend this to Windows users), Node.js command prompt or even Windows cmd itself. Hope to have helped you. Best wishes!
The solution is to install GIT bash and avoid
using MinTTY and follow the documentation. Here is the solution:
Uninstall existing GIT bash Reinstall GIT bash Set up during
installation:
Select Use Git from the Windows Command Prompt
Select Checkout Windows-style, commit Unix-style line endings
Select Use Windows' default console window
Okay this works for sure -
Go to https://cygwin.com/install.html and download either the
32 or 64 bit version of Cygwin.
Run the install and install it onto one of your drives.
Run the Cygwin.bat and you will get the same command line
interface.
When you run bower init, it will work just fine. The Mintty that
comes with GIT is broken for somethings. Use the shell that comes
with Cygwin and you will be fine.
It works for me no problem. I used the 64 bit version on a Window 8 64bit OS. Good Luck!
You're most likely running C:\Program Files\Git\git-bash.exe and can instead run C:\Program Files\Git\bin\bash.exe to eliminate the issue. This avoids having to install another yet another terminal.