Why is Xilinx 2014.4 SDK so buggy on Linux?

I am running CentOS 6.6 with Vivado and SDK, but SDK has been crashing like crazy on me. It dies with the following message.

java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion `NOT_REACHED' failed.

Turns out it is a problem with versioning between gtk2 and cairo. Here is a link with the details.

There are some posts on the Xilinx forum about installing updated RPMs to fix this, but it is not a good idea to install RPMs outside of the YUM framework. Another alternative is to disable cairo in eclipse. So edit your eclipse configuration file in install_dir/SDK/2014.4/eclipse/lnx64.o/configuration/config.ini (and the 32-bit version if that is appropriate) to include the following line.


This seems to have fixed things at least for now.

5 thoughts on “Why is Xilinx 2014.4 SDK so buggy on Linux?

  1. Hi, whoever you are, many thanks for the post of this workaround. We have been trying to use vivado_hls and SDK on CentOS 6.6 for the last few days, and both have been crashing whenever we try to view a source file. But for both, the fix you outlined seems to be working!

  2. Glad I could help. It’s kind of frustrating that Xilinx doesn’t test their builds on a more recent version of CentOS. 2014.4 came out long after CentOS 6.5 was no longer the latest release. It is especially problematic since people just have to do a yum update to have their machine upgraded to 6.6.

  3. But then you need to remember to type that all the time. Or make an alias. It would be nice if Xilinx actually tried to make tools that could run on a variety of Linux platforms and not just hide behind the excuse of “that is not a supported OS”.

  4. We load our Xilinx revisions up on a locked server, so there’s no editing the INI files. Xilinx has traditionally had a “software” issue. They were pulled kicking and screaming into Linux. And, all their tools have been buggy. They have finally started putting some money into software.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.