Mic92/blog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix link, add alternative solution

Browse Source
This commit is contained in:
Albert.Schulz 2017-04-13 20:30:34 +02:00
parent 53830e5aa8
commit acb2139b7b
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
View File

@ -18,7 +18,11 @@ $ ln -s /bin/bash ~/.local/bin/sh
``` ```
Thanks to ole2 for providing this solution in the xilinx forum, which you can find here: Thanks to ole2 for providing this solution in the xilinx forum, which you can find here:
[forum post](https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-2-Launching-jobs-on-a-remote-host) [forum post](https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-2-Launching-jobs-on-a-remote-host/td-p/396861)
As he points out, this seem to be a bug in Vivado. Vivado seems to call a script with #!/bin/sh and expects a bash to be executed. But for Ubuntu, /bin/sh points to /bin/dash per default. An alternative solution is to re-configure this link using:
```bash
$ sudo dpkg-reconfigure dash
```
As he points out, this seem to be a bug in Vivado.
I had this issue in Vivado 2016.4 and Ubuntu 16.04 LTS. I had this issue in Vivado 2016.4 and Ubuntu 16.04 LTS.