10-06-2015 09:18 PM
When trying to install Xilinx_Vivado_SDK_Lin_2015.3_0929_1 the installation hans at the message "generating installed device list". I let it run for hours and it never finished.
I'm using arch linux with the following kernel:
Linux Arch 4.2.2-1-ARCH #1 SMP PREEMPT Tue Sep 29 22:21:33 CEST 2015 x86_64 GNU/Linux
Also if i kill the installer and try to run any binary from /opt/Xilinx it fails with a missing library message. By example:
couldn't load file "librdi_commontasks.so": libncurses.so.5: cannot open shared object file: No such file or directory
I suppose this happens because my libncurses library is version 6. I can workaround this installing ncurses version 5 from source. But I don't know how to start the design tools from command line, is there any documentation on this.
10-06-2015 10:08 PM - edited 10-06-2015 10:11 PM
Check this answer record: http://www.xilinx.com/support/answers/60111.html
If the above answer didn't help, share the xinstall_xxxxx.log file here located in /opt/Xilinx/.xinstall
10-14-2015 04:23 AM
10-14-2015 04:28 AM
@felknight: For calling the xilinx binaries, you need to source the settings64.sh script first, which is located in [whereever]/Vivado/2015.3/settings64.sh. However, it seems that these scripts are generated by the installer during this last phase. When fixing the ncurses5 issue, the scripts will be available and calling them from command line works well...
11-11-2017 02:30 AM
This is still the case for some distros in 2017.3 as well.
INFO : Running post-install tasks....... tail -f .Xilinx/xinstall/xinstall_1510382829539.log 2017-11-11 08:23:43,312 DEBUG: o.p:? - Executing script Generating installed device list: /tools/xilinx/vivado/v2017.3/Vivado/2017.3/bin/vivado [-nolog, -nojournal, -mode, batch, -source, /tools/xilinx/vivado/v2017.3/.xinstall/Vivado_2017.3/scripts/xlpartinfo.tcl, -tclargs, /tools/xilinx/vivado/v2017.3/Vivado/2017.3/data/parts/installed_devices.txt]
The above happens both in GUI and batch mode.
Why isn't the installation done in two stages (internally) if LD_LIBRARY_PATH or similar has to be set to match the installation.
The reason it's hanging seem to be that it can't load it's own libraries during the last stage. While the installation is hanging it's possible to complete it manually:
LD_LIBRARY_PATH=/export/filestore/tools/xilinx/vivado/v2017.3/Vivado/2017.3/lnx64/tools/clang-3.9/lib /tools/xilinx/vivado/v2017.3/Vivado/2017.3/bin/vivado -nolog -nojournal -mode batch -source /tools/xilinx/vivado/v2017.3/.xinstall/Vivado_2017.3/scripts/xlpartinfo.tcl -tclargs /tools/xilinx/vivado/v2017.3/Vivado/2017.3/data/parts/installed_devices.txt
But, when you then break xsetup it will clean up by removing the installation leaving behind nothing but the .xinstall directory.
I remember the good old days on Solaris when the Xilinx installer was basically a tar/cpio style extraction. Then the bloated Java based installer which took hours and hours to do the same job came along...
01-05-2018 06:04 AM
You can add the library path before installation (2017.4):
01-20-2018 01:07 AM
Good idea. It works in the 2017.4 release. It's a bit odd that the installation script does not do this internally by itself.
01-23-2018 06:32 AM
Thanks a lot for letting us know and we are glad to see your issue is resolved now using the workaround provided in the previous post.
As your issue is solved, please mark the response as Accepted Solution, so the topic can be completed then. We appreciate your help.
Thanks in advance and have a great day.
10-21-2019 02:32 AM
Hello, I confronted the same problem. When I try to generate the installing device list manually. I found that
The log file shows that
2019-10-21 17:10:06,697 DEBUG: o.p:? - Executing script Generating installed device list: /home/yujie6/Vivado/2018.3/bin/vivado [-nolog, -nojournal, -mode, batch, -source, /home/yujie6/.xinstall/Vivado_2018.3/scripts/xlpartinfo.tcl, -tclargs, /home/yujie6/Vivado/2018.3/data/parts/installed_devices.txt]
It really made me headache, please help me... I'm using Ubuntu 19.04.
10-30-2019 03:03 AM
Hello @yujie6 ,
Please check this forum topic, that has a workaround that you can use/try at your end that should also help you to overcome your issue:
Hope this helps.