cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
1,189 Views
Registered: ‎03-12-2018

BUG: Vivado: fails to start when called via symlink

When called via symlink (eg. /usr/bin/vivado -> {{vivado_install_dir}}/Vivado/2017.1/bin/vivado), the startup script guesses the installation directory wrong. Using symlinks is a very common approach in Unix world (eg. for Debian's alternatives system).

 

Picking the dirname from $0 is completely wrong here. $0 holds the name the program is called as, *not* the actual pathname of the actual text file ! (there're lots of situations where these do *not* match, symlinks is just one of them).

 

A more correct approach would be doing a reverse (inode->pathname) lookup on the file. For the symlink'ed case, always following the links would also do it.

 

OTOH, a really clean solution would be

a) generating proper startup scripts (w/ actual pathes) on install stage

b) always use a *fixed* install prefix (eg. /opt/vivado/<version>/) and drop the whole idea of installation specific prefixes.

 

0 Kudos
2 Replies
Highlighted
Moderator
Moderator
1,106 Views
Registered: ‎11-09-2015

HI @metux,

 

We don’t support symlink so this is not a bug.


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Highlighted
Visitor
Visitor
1,071 Views
Registered: ‎03-12-2018

So, you don't support one of the very basic and common Unix concepts.

 

I'd recommend consulting a seasoned Unix operator for an introduction to the basic concepts.

0 Kudos