Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unbound variable `DOTNET_INSTALL_DIR` in `eng/restore-toolset.sh`
See original GitHub issueSteps to reproduce
git clone https://github.com/dotnet/clicd cli./build.sh./build.sh
Expected behavior
The second build should succeed.
Actual behavior
eng/restore-toolset.sh: line 46: DOTNET_INSTALL_DIR: unbound variable
Workaround
DOTNET_INSTALL_DIR=$(pwd)/.dotnet ./build.sh
Environment data
Repros on macOS 10.14 and Ubuntu 16.04.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Unbound variable error from the latest version of dotnet- ...
The script exits with error due to an unbound variable. The code there seems to be assuming that the variable is set but...
Read more >Getting unbound variable error in shell script
This threw the unbound variable issue. However, if I defined filename above set -eu to an empty string, the issue disappeared.
Read more >Bash throws error, line 8: $1: unbound variable
I am trying to learn how to use getopts so that I can have scripts with parsed input (although I think getopts could...
Read more >missing_deps: unbound variable -- Nord GNOME Terminal ...
I've verified I have dconf installed as well as uuid. Not sure what's causing the issue with installing the GNOME terminal theme.
Read more >Q2cli: ZSH_VERSION unbound variable error
When activating a qiime2 2018.11 conda environment from within a bash script that has the -u option activated, q2cli's tab completion hook ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This should have been fixed by https://github.com/dotnet/cli/pull/10653.
There is another commit there. I just fixed it together in the same PR, but separate commits. This was the commit for the CLI: https://github.com/dotnet/cli/pull/10653/commits/01303586fc03aedfd5d703cdc7a858fa9a7a798c