Vivado 2018.03 and DocNav on Debian 10 (Buster)

  |   Source

Late last year the ageing effects of my old GNU/Linux desktop system became so severe that ignoring them would soon not be an option anymore. One of the hard disks gave me troubles a while ago and although I was able to fix it so that finally the extended SMART test passes again without errors, it continues to report errors in the form of "unreadable (pending) sectors". The on-board USB controller reports errors for one of the internal USB ports for even longer and one DDR3 module was replaced even before that as diagnosed by the wonderful Memtest86.

On top of all this, the "Club 3D Radeon X1300PRO" dual DVI graphics card started to hang the whole system a few seconds after waking up from suspend. Or at least I think it was the graphics card as the system never recorded error messages in the logfiles, but the display visibly degraded and I think I saw some drm error message flash by at some point. Be that as it will, I was glad that I got the chance to replace the system in time and gradually move stuff off a functioning system instead of attaching disassembled hard disks to a new system.

The AMD Ryzen 5 system from ARLT Computer, available without Windows, looked like very good value for my money and together with an HDMI to DVI adapter it should also easily power my two DVI monitor setup.

With Debian Buster on the horizon, it was clear that I wanted to go for this, as the 4.9.0 Linux kernel from Debian Stretch is not brand new anymore and may have problems with the new hardware. All in all things went well until I tried to install the latest Xilinx toolchain that worked

reports a daily SMART error although I manually fixed the nurecoverable become so severe that tshowing effects of ageing. Fortunately it showed signs of decay I took the liberty Having installed Vivado 2017.04 on one of my GNU/Linux machines that run Debian 9.3 (Stretch), I realized that DocNav fails to start:

dzu@deepthought:~$ . /opt/Xilinx/Vivado/2017.4/settings64.sh
dzu@deepthought:~$ docnav
docnav: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
dzu@deepthought:~$
Xilinx Logo

It turns out that Stretch currently does not carry libpng in version 12 and that the corresponding package from Jessie cannot be installed correctly:

dzu@deepthought:~$ sudo dpkg --install ~/Downloads/libpng12-0_1.2.50-2+deb8u3_amd64.deb
(Reading database ... 273874 files and directories currently installed.)
Preparing to unpack .../libpng12-0_1.2.50-2+deb8u3_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.50-2+deb8u3) ...
dpkg: error processing archive /home/dzu/Downloads/libpng12-0_1.2.50-2+deb8u3_amd64.deb (--install):
 unable to install new version of '/usr/lib/x86_64-linux-gnu/libpng12.so.0': No such file or directory
Errors were encountered while processing:
 /home/dzu/Downloads/libpng12-0_1.2.50-2+deb8u3_amd64.deb
dzu@deepthought:~$

For me the solution was to download libpng12-0 from Wheezy and install it. Now DocNav runs without any further problems.

One should keep in mind that this package has some known CVEs associated with it, but given that it will only be used by DocNav and this only shows data provided directly by Xilinx, the risk of doing so is qualified. DocNav should really move to a newer version of libpng to fix this completely.

Also note that DocNav was only recently ported to 64 bit, so some of the available information on the Xilinx website is no longer accurate, especially the DocNav part of Answer Record #66184.

Comments powered by Disqus