Package Details: vivado 2024.2-1

Git Clone URL: https://aur.archlinux.org/vivado.git (read-only, click to copy)
Package Base: vivado
Description: FPGA/CPLD design suite for AMD devices – Vivado edition
Upstream URL: https://www.xilinx.com/products/design-tools/vivado.html
Licenses: custom
Conflicts: vitis
Submitter: xiretza
Maintainer: VitalyR (leuko)
Last Packager: leuko
Votes: 17
Popularity: 0.031913
First Submitted: 2019-06-18 22:23 (UTC)
Last Updated: 2024-11-20 22:25 (UTC)

Pinned Comments

leuko commented on 2024-01-14 21:14 (UTC) (edited on 2024-09-26 06:41 (UTC) by leuko)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 14 Next › Last »

Lacsapix commented on 2024-06-06 08:54 (UTC) (edited on 2024-06-06 08:54 (UTC) by Lacsapix)

Today I've tried the 2024.1 version and all my segfault problems with 2023.x are gone.

Lacsapix commented on 2024-06-05 06:29 (UTC) (edited on 2024-06-05 12:49 (UTC) by Lacsapix)

@ph_l, I can confirm that your "fix" does indeed work. It seems like a gcc-libs issue. Thank you very much for your effort!

EDIT:Right so after messing around a bit, I found out that vivado still crashes. But a bit different now. When building certain IP-cores the process still segfaults

segfault in YOUR_PATH_HERE/2023.2/bin/unwrapped/lnx64.o/vivado -exec vivado -log IP_CORE_NAME_HERE.vds -m64 -product Vivado -mode batch -messageDb vivado.pb -notrace -source IP_CORE_NAME_0.tcl, exiting...

ph_l commented on 2024-06-04 14:47 (UTC)

@lacsapix, had the same issue. The coredump pointed to the segault in libtcmalloc. Got it "fixed" by using the system's libtcmalloc, which is in gperftools, which also requires to use a newer version of libstdc++:

 pacman -S gperftools
 mv /opt/Xilinx/Vivado/2023.2/lib/lnx64.o/Default/libstdc++.so.6 /opt/Xilinx/Vivado/2023.2/lib/lnx64.o/Default/libstdc++.so.6.safe
 mv /opt/Xilinx/Vivado/2023.2/lib/lnx64.o/libtcmalloc.so.4 /opt/Xilinx/Vivado/2023.2/lib/lnx64.o/libtcmalloc.so.4.safe

Not sure if this breaks other things, but synthesis does not segfault anymore.

leuko commented on 2024-05-28 15:36 (UTC)

@lacsapix I compared the versions. Only gtk3 differs. I have 3.24.41-1. I don't have fxload.

Lacsapix commented on 2024-05-28 07:00 (UTC) (edited on 2024-05-28 07:01 (UTC) by Lacsapix)

@leuko: Glad to hear I'm not entirely insane. Can you post your dependency versions?

# pacman -Q cpio gtk3 inetutils lib32-libpng12 libpng12 libxcrypt-compat ncurses5-compat-libs xorg-xlsclients fxload
cpio 2.15-1
gtk3 1:3.24.42-1
inetutils 2.5-1
lib32-libpng12 1.2.59-2
libpng12 1.2.59-2
libxcrypt-compat 4.4.36-1
ncurses5-compat-libs 6.4-2
xorg-xlsclients 1.1.5-1
fxload 1.0.26-1

leuko commented on 2024-05-27 17:00 (UTC)

@Lacsapix: I have a working installation, however my installation is from couple of months ago. Try to build in clean chroot and try there.

@Omid:

  1. I don't have any idea about your problem :/
  2. Can you please explain why lsb_release is required?

Omid commented on 2024-05-26 07:21 (UTC) (edited on 2024-05-26 07:23 (UTC) by Omid)

I get the following output, and creating pkg stuck at the last line (Copying source files needed for debug symbols...). Any idea

==> Making package: vivado 2023.2-1 (Sun 26 May 2024 12:16:56 PM +08)

==> Checking runtime dependencies...

==> Checking buildtime dependencies...

==> Retrieving sources...

-> Found FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz

-> Found spoof_homedir.c

==> Validating source files with md5sums... FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz ... Passed spoof_homedir.c ... Passed

==> Extracting sources...

-> Extracting FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz with bsdtar

==> Starting prepare()...

==> Starting build()...

==> Entering fakeroot environment...

==> Starting package()...

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

This is a fresh install. INFO Could not detect the display scale (hDPI). If you are using a high resolution monitor, you can set the insaller scale factor like this: export XINSTALLER_SCALE=2 setenv XINSTALLER_SCALE 2 Running in batch mode... Copyright (c) 1986-2022 Xilinx, Inc. All rights reserved. Copyright (c) 2022-2024 Advanced Micro Devices, Inc. All rights reserved. INFO - User has accepted the EULAs. WARN - Warning: you are running on an OS version that is not officially supported. AMD does not recommend installing on unsupported OSes. INFO - Installing Edition: Vitis Unified Software Platform INFO - Installation directory is /mnt/Data/vivado/pkg/vivado/opt/Xilinx

Installing files, 99% completed. (Done)
It took 2 h and 4 m(s) to install files. WARN -

## Execution of Pre/Post Installation Tasks Failed

Warning: AMD software was installed successfully, but an unexpected status was returned from the following post installation task(s) xargs: file: terminated by signal 31 sed: no input files INFO - Installation completed successfully.For the complete setting to use Versal ACAP tools, please run the script "installLibs.sh" under /mnt/Data/vivado/pkg/vivado/opt/Xilinx/Vitis/2023.2/scripts, which requires the root privilege.

==> Tidying install...

-> Removing libtool files...

-> Purging unwanted files...

-> Removing static library files...

-> Copying source files needed for debug symbols...

Omid commented on 2024-05-26 04:03 (UTC)

Please add lsb_release to dependencies.

Lacsapix commented on 2024-05-16 09:14 (UTC)

Hi! In February I reported that this package doesn't work on a recently updated system. As of today I'm still unable to get Vivado >=2023 running (past synthesis). Can somebody confirm that they have Vivado 2023 running on their system? And if so, post their dependency versions or other relevant information?

« First ‹ Previous 1 2 3 4 5 6 7 .. 14 Next › Last »