Fedora 37 is not officially supported by Xilinx (or AMD, I should say). Hence, I had to use some workarounds to install it on my work machine.

These instructions have been tested for the 2022.2 and 2023.1 versions.

Why Vitis/Vivado?

Vitis HLS and Vivado are freeware! This means that the tool itself is not open source, but anyone can download it and use it! I use it in my research and I find it useful to be able to run some small testbenches on my local machine without ssh-ing to the lab server.

Downloading the web installer

First of all, you need to download the Vitis Linux web installer, available at this page. I chose the Vitis Core Development Kit - 2022.2 package, and saved it in my ~/Downloads directory.

Running the installer

First of all, we make the installer executable:

fab@fedora:~ $ cd ~/Downloads
fab@fedora:Downloads $ chmod u+x ./Xilinx_Unified_2022.2_1014_8888_Lin64.bin

Then, we follow the instructions in this post (search for vlntmrx answer). We extract the installer in a folder called xilinx using the following command:

fab@fedora:Downloads $ ./Xilinx_Unified_2022.2_1014_8888_Lin64.bin --target xilinx

The installer will run and crash, but a folder xilinx will be there with all the stuff that we need:

fab@fedora:Downloads $ cd xilinx
fab@fedora:xilinx $ ls
bin  data  hs_err_pid811776.log  lib  tps  xsetup

Now, we execute the following commands:

# Removing the harzbuff library that is causing the crash
fab@fedora:xilinx $ rm ./tps/lnx64/jre11.0.11_9/lib/libharfbuzz.so
# Creating a symlink to my system harbuzz library.
fab@fedora:xilinx $ cp -s /lib64/libharfbuzz.so.0 ./tps/lnx64/jre11.0.11_9/lib/libharfbuzz.so
# Running the installer using xsetup.
fab@fedora:xilinx $ ./xsetup

The Xilinx GUI installer should start now. In my case, I choose /eda/xilinx as installation path, executing the following commands to create it:

fab@fedora:xilinx $ sudo mkdir /eda # Creating the folder.
fab@fedora:xilinx $ sudo chown fab /eda # Changing user ownership of the folder.
fab@fedora:xilinx $ sudo chgrp fab /eda # Changing group ownership of the folder.
fab@fedora:xilinx $ mkdir /eda/xilinx

In the GUI installer, provide /eda/xilinx as installation path.

Vitis HLS GUI

Now, we need to do some other things to allow the Vitis HLS GUI to start. We will follow the instructions shown in this post.

First of all, we move to the Vitis HLS path where we need to change some thins: /eda/xilinx/Vitis_HLS/2022.2/lib/lnx64.o/Default:

fab@fedora:xilinx $ cd /eda/xilinx/Vitis_HLS/2022.2/lib/lnx64.o/Default
fab@fedora:Default $

Here, we rename the Xilinx version of libstdc++.so.6 to libstdc++.so.6.bak:

fab@fedora:Default $ mv libstdc++.so.6 libstdc++.so.6.bak

Then, we copy the system version of libstdc++.so.6 here via a symbolic link:

fab@fedora:Default $ ln -sf /usr/lib64/libstdc++.so.6 ./libstdc++.so.6

Now the GUI should work! Run in the terminal:

fab@fedora:Default $ cd
fab@fedora:~ $ source /eda/xilinx/Vitis_HLS/2022.2/settings64.sh
fab@fedora:~ $ vitis_hls

The following image is what you should see:

Change ld in Vivado

When trying to run a C compilation in Vitis HLS, you might get the following error:

/eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld: /lib64/libm.so.6: unknown type [0x13] section `.relr.dyn'
/eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld: skipping incompatible /lib64/libm.so.6 when searching for /lib64/libm.so.6
/eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld: cannot find /lib64/libm.so.6

To fix this, we simply have to change the ld binary with the system one. To do that, we first create a backup copy of ld:

fab@fedora:~ mv /eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld /eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld.bak

Then, we create a symbolic link to /usr/bin/ld:

fab@fedora:~ ln -s /usr/bin/ld /eda/xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bin/ld

Now everything should work!

Conclusions

You can do the same for Vivado and Vitis. Thanks to the Xilinx community for the help!