Arch Linux User Repository

PKGBUILD cannot download Vivado, you have to download Vivado before executing the PKGBUILD. Refer to PKGBUILD.

This PKGBUILD is also able to install Vitis with some errors, however there is a standalone package called vitis AUR which seems to be more advanced than the installation in this PKGBUILD.

You are right, qwjyh; thanks for confirmation — I also get the error. LD_PRELOAD=libfakeroot.so, however it cannot be found, even I think it is set by makepkg automatically.

I applied not @microsparky's solution and the libfakeroot.so messages are gone.

Note that even the packaging went fine, I did not test Vivado or Vitis runtime.

Hi leuko. I tried to install Vivado 2023.1 using the latest PKGBUILD with editted source and md5sums. I had the same issue on LD_PRELOAD as Microsparky reported.

Also, for those who want to install old versions, Vivado 2023.1 contains old java (jr317.0.3), which seems to have a bug on the latest Linux kernel and doesn't work.

Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.xilinx.installer.api.InstallerLauncher.<clinit>(Unknown Source)
Caused by: java.lang.NullPointerException: Cannot invoke "jdk.internal.platform.CgroupInfo.getMountPoint()" because "anyController" is null
...

I replaced **/tps/lnx64/jre17.0.3_7/bin with symlink to /bin and fixed --config argument in PKGBUILD then successfully built the package.

p.s. I made a mistake: 2020.1 -> 2023.1

Thanks for sharing microsparky!

I did not have any issues with desktop files and LD_PRELOAD before. If others also share similar issues, we can look into that.

Hello Leuko, first thank for maintaining! I had some issues during the build first with LDPRELOAD then with *.desktop files. I don't really know what to do with my 'fixes' but maybe they are insightful to you or help someone else get unstuck anyway below are my findings:

LD_PRELOAD should already contain libfakeroot.so but on my system for whatever reason its was not being found so I hard coded LD_PRELOAD in the PKGBUILD:

LD_PRELOAD=$srcdir/spoof_homedir.so:/lib/libfakeroot/libfakeroot.so

*.desktop files were not being found at "$srcdir"/installer_temp/Desktop instead they were found at $srcdir"/installer_temp/.local/share/applications and $srcdir"/installer_temp/.config/autostart/applications so I changed the for loop to the following:

for deskfile in "$srcdir"/installer_temp/.local/share/applications/*.desktop; do

likewise I added another loop for the file in .config/autostart:

for deskfile in "$srcdir"/installer_temp/.config/autostart/applications/*.desktop; do

One more thing is I added some code to these loops to change the names to be more consistent as follows:

# Extract directory and filename
    filepath=$(dirname "$deskfile")
    filename=$(basename "$deskfile")

    # Rename the file:
    # 1. Remove underscores followed by numbers (e.g., `_123`)
    # 2. Replace spaces with hyphens
    # 3. Convert to lowercase
    # 4. Ensure the filename starts with `xilinx-`
    filename=$(echo "$filename" | sed -E 's/_[0-9]+//g' | tr ' ' '-' | tr '[:upper:]' '[:lower:]')
    if [[ "$filename" != xilinx-* ]]; then
        filename="xilinx-$filename"
    fi

    # Construct the new file path
    newdeskfile="$filepath/$filename"

    # Rename the file (move it to the new name)
    mv "$deskfile" "$newdeskfile"

    # Install the renamed file to the target directory
    install -Dm644 "$newdeskfile" -t "$pkgdir/usr/share/applications/"

Good catch Alex, thanks!

Your idea makes sense. Now, vitis_ provides vivado and will conflict with other packages that provide vivado or vitis. vivado provides vivado and will conflict with other packages providing vivado.

I did not increment the version to save CO2, please rebuild if you need this update. I could not test it, feedback welcome.

The package_vitis_ function still has a hardcoded 2024.1 version in some places, which causes it to fail.

It would also be useful to add vivado to the provides of vitis_, so other packages that depend on vivado can be used when we have vitis installed via this package.

    sed -i \
        "s|\$CUSTOM_LIBRARY_PATH|$_installprefix/Vitis/2024.1/tps/lnx64/cmake-3.24.2/libs/Ubuntu|g" \
        "$pkgdir$_installprefix"/Vitis/2024.1/bin/vitis
    sed -i \
        "s|\$MY_LIBRARY_PATH|$_installprefix/Vitis/2024.1/tps/lnx64/cmake-3.24.2/libs/Ubuntu|g" \
        "$pkgdir$_installprefix"/Vitis/2024.1/bin/vitis

Update on the fonconfig "bug". The issue is fixed with the now available fontconfig 2:2.16.0-2.

@Lacsapix, thanks for the heads up. The fix appears to work for me as well. I assume you were encountering an issue where it would crash from a grey splash too?

There is a bug (I think) when upgrading fontconfig to 2:2.16.0-1. Downgrading to 2:2.15.0-2 works for now. https://archive.archlinux.org/packages/f/fontconfig/fontconfig-2%3A2.15.0-2-x86_64.pkg.tar.zst

This is a good idea, I just have been reluctant to do this because of the complexity, e.g., I don't want to test the effects on non-KDE or non-Wayland environments.

I would also like to merge QT_AUTO_SCREEN_SCALE_FACTOR with https://wiki.archlinux.org/title/Xilinx_Vivado#Vivado_shows_an_empty_screen_on_Sway

I use Sway, but I don't have Docnav. Can someone with KDE and someone else with X11 try the following line on Vivado and Docnav?

Without _JAVA_AWT_WM_NONREPARENTING you see a blank Vivado window on Sway.

/usr/share/applications/Vivado 2024.2.desktop:

...
Exec=bash -c '[ "$XDG_SESSION_TYPE" = "wayland" ] && export _JAVA_AWT_WM_NONREPARENTING=1 QT_AUTO_SCREEN_SCALE_FACTOR=1; exec /opt/Xilinx/Vivado/2024.2/bin/vivado'
...

After the test I can merge these.