@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:
- I don't have any idea about your problem :/
- Can you please explain why
lsb_release
is required?
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, vivado |
Submitter: | xiretza |
Maintainer: | VitalyR (leuko) |
Last Packager: | leuko |
Votes: | 19 |
Popularity: | 0.26 |
First Submitted: | 2019-06-18 22:23 (UTC) |
Last Updated: | 2025-03-07 08:57 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 16 Next › Last »
@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:
lsb_release
is required?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...
Please add lsb_release to dependencies.
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?
You don't actually have to download the entire (now over 100 GiB) unified installer.
The self-extracting web installer (~300 MiB) can create a customised bundle identical to the unified installer - thus only downloading the components you require.
I've written down what I did to install Vivado and support for Artix 7 only in this gist.
I am against including 2023.2.2
patch in the PKGBUILD
. This is only a patch for newer devices. I guess less than 10% of the package users need this patch. (So I unflagged the package.)
From the installation page:
...
For customers using these devices, AMD recommends installing Vivado 2023.2.{1,2} For other devices, please continue to use Vivado ML 2023.2.
@Lacsapix and @miree Can confirm. After "pacman -Syu" Vivado keeps crashing during synthesis with the Seg Fault mentiones. Can also confirm that 2023.2 and 2023.1 have this problem (with or without the license environment variables), while 2022.2 works as usual.
@Lacsapix
I had the same issue today trying to use vivado (older version 2023.1, not latest 2023.2) after a recent "pacman -Syu".
The segfault disappears when I don't set LM_LICENSE_FILE and XILINXD_LICENSE_FILE environment variables.
Hi everyone! After yesterdays "pacman -Syu" I keep getting the same error during synthesis: "/opt/Xilinx/Vivado/2023.2/bin/rdiArgs.sh: line 369: 33600 Segmentation fault (core dumped) "$RDI_PROG" "$@""
Line 369 in rdiArgs.sh is the following if function:
RDI_EXEC_COMMANDS() {
if [ -f $RDI_PROG ]; then
"$RDI_PROG" "$@"
fi
return
}
Vivado 2022.2 seems to be working great, its just 2023.2. Is anyone else having this same issue or is this just a me-problem?
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 thePKGBUILD
. Refer toPKGBUILD
.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 thisPKGBUILD
.