I am attempting to install .Net Core on my OSX laptop and following the instructions at https://dotnet.github.io/getting-started/. I've downloaded the PKG and installed it successfully (along with its dependency OpenSSL). However, when I attempt to run dotnet from the command line I get a command not found error.
What should I do to fix this and get the dotnet CLI to be installed properly?
I think the installer had some symbolic links missing on post-installation, there is already a fix for this but not sure if it is in the latest pkg as the time of writing.
You could create the symbolic links yourself:
$ ln -s /usr/local/share/dotnet/bin/dotnet /usr/local/bin/
$ ln -s /usr/local/share/dotnet/bin/csc /usr/local/bin/
Hope that helps
to today work this for me
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
Well, it's a bit weird but I had the same problem and the only thing I did was reopening the terminal and writing dotnet new mvc then it worked like a charm!
Thanks to the answer on Github issue given by flyingsky in the following link: Command not found dotnet Github issue
Related
I recently followed the steps to install jENV and Corretto-8. Unfortunately now whenever I open a new terminal I see the following:
Last login: XXXXXXX
/Users/username/.zshrc: command not found: jenv
/Users/username/.zshrc: command not found: jenv
Does anyone know how to fix this? I am truly at a loss.
This problem is likely occurring because jenv has not been added to your PATH before jenv init runs. Look at your .zshrc file and ensure the jenv section looks like this
export PATH="$HOME/.jenv/bin:$PATH"
eval "$(jenv init -)"
Also, be sure that you don't have multiple jenv sections since the installation instructions for Zsh are not re-runnable. If you accidentally ran the instructions for Zsh twice, you will find two jenv sections at the end of your .zshrc file and you should delete one of them.
Today I was running into the same problem. I installed jenv via brew but it showed every time: "command not found".
The solution was, that jenv wasn't linked. So I run the following command and everything worked after that:
brew link jenv
You might have installed it using MacOS brew and did this as well:
$ echo 'export PATH="$HOME/.jenv/bin:$PATH"' >> ~/.bash_profile
$ echo 'eval "$(jenv init -)"' >> ~/.bash_profile
Now, you will have a duplicate command in your bash. Remove those two lines in your bash and you should be good.
When I tried to open vscode in WSL bash on Ubuntu 20.04 using command code ., it failed and the following message was logged:
/mnt/c/Users/john/.vscode/extensions/ms-vscode-remote.remote-wsl-0.50.1/scripts/wslCode.sh: 57: /home/john/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/bin/code: not found
I would like to ask how to fix this problem? Thx a lot!
I found the solution. Even though I think that you've already know it.
You need to delete the folder /home/john/.vscode-server/ with sudo rm -rf /home/john/.vscode-server.
Then, you just run code . or try to open any project that you want it.
Then a script will load and will install a new .vscode-server in your machine with the right files.
I want to complete the setup in Visual Studio Code for Pixhawk 4 development. So I followed the steps given in this documentation below. I also installed the Cygwin Toolchain previously.
https://dev.px4.io/master/en/setup/vscode.html
After opening the Firmware folder in vsc, I installed all recommended extensions. Then I selected the kit and clicked on build using the blue bar in the bottom to configure the project. Right after that, I got this error:
Bad CMake executable "". Is it installed or settings contain the correct path (cmake.cmakePath)?
What might be causing the problem? I am a beginner so if anything is unclear about the question please ask me for it. Thanks for all the help.
There is an issue with the path having a space in it apparently. Lots of people have run into this, but it has yet to be fixed (I just hit it myself earlier today). The "solution" (read: workaround...because Microsoft... 🙄) is to reinstall Cmake in a different directory (one with no spaces, obviously 😉), and to ensure that it is in your system path.
See this Github issue for extensive troubleshooting/discussion.
I had the same problem when I updated VSCode. In the project setting I put the full path of Cmake like:
"cmake.cmakePath": "/usr/local/bin/cmake"
And it worked.
I had the same problem and could solve it by (re)installing cmake:
sudo apt install cmake
If gcc is not installed, you need to install gcc first and then install cmake.
install gcc
sudo apt install build-essential
Download CMake from https://cmake.org/download/
Install CMake
$ ./bootstrap
$ make
$ make install
After this step try again and it should work.
I'm following the Django installation tutorial for Windows. I ran the installation command below and it worked fine.
pip install virtualenvwrapper-win
However, when I try running mkvirtualenv myproject I get an error saying bash: mkvirtualenv: command not found
I am running Git Bash on Windows. I found a solution for the Windows Command Prompt here, but I was hoping to use Git Bash, because I'm much more familiar with it.
Thanks!
Maybe it is too late to answer this, but let me put my anser here anyhow.
I ran the pip install command twice, and finally everything is working for me. Just run "pip install" line this:
First do it: "pip install virtualenv virtualenvwrapper"
Second, do it: "pip install virtualenvwrapper-win"
Everything should be fine after that.
1) I installed virtualenv using pip.
2) I ran the command virtualenv venv
3) Then I ran source venv/bin/activate but it says that there is no such file or directory.
When I cd into venv/bin I find 3 things - python, python 2.7, and python 3.5. Does anyone know the problem?
i have had the same problem. and what i did is just run the command
virtualenv env
again. And then more files were generated under directory env/bin, including the activate file. it's so weird.
I solved the similar problem running python3.7 -m venv venv, you can change for your version of python that is installed in your enviroment.
According to Python doc, the installation step is
$ python3 -m pip install --user virtualenv
$ python3 -m venv env
The last command gives a warning message,
The virtual environment was not created successfully because ensurepip is not
available. On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.
apt-get install python3-venv
You may need to use sudo with that command. After installing the python3-venv
package, recreate your virtual environment.
$ sudo apt-get install python3-venv
Now, activate is available.
I solved a similar problem by naming it venv2 when I ran virtualenv. I already had a virtual environment named venv for another project. This allowed me to proceed.
I experienced this problem when using the --upgrade option. Removed the option, and all ran as expected.
I double it is caused by some networking issue, I run it twice to get 'activate' script installed. Maybe first it can't connect to some source so it just abort installation.
I had this happen on rasbian when I hadn't installed python3-pip before creating the venv.