must be modified:
_srcname=FPGAs_AdaptiveSoCs_Unified
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 10 11 .. 16 Next › Last »
must be modified:
_srcname=FPGAs_AdaptiveSoCs_Unified
After comparing with a installation in my ubuntu 22.04 nspawn, I find a new way to launch vitis HLS 2023.1 which works for me:
Do not apply the old hacking to replace '=' to '<' in autopilot_init.tcl
, it seems to cause vitis hls to load internal buggy libraries...
sed -i -e "28s|Default|ubuntu|" "/opt/Xilinx/Vitis_HLS/2023.1/bin/ldlibpath.sh"
, just to fake us to be a ubuntu distro when search library.
And gtk3
should be a new dependency. (pacman -S gtk3
)
I don't actually try to build it again in a clean chroot, but I need apt install libgtk-3-common
in ubuntu 22.04 to get libgtk-3.so.0
, so I think it also need gtk3
here.
Fail to launch vitis hls(2023.01) on my machine. It only shows that:
phanium@arch ~/x/t/tmp (dev) [1]> /opt/Xilinx/Vitis_HLS/2023.1/bin/vitis_hls
****** Vitis HLS - High-Level Synthesis from C, C++ and OpenCL v2023.1 (64-bit)
**** SW Build 3854077 on May 4 2023
**** IP Build 3864474 on Sun May 7 20:36:21 MDT 2023
**** SharedData Build 3865790 on Sun May 07 13:33:03 MDT 2023
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2023 Advanced Micro Devices, Inc. All Rights Reserved.
source /opt/Xilinx/Vitis_HLS/2023.1/scripts/vitis_hls/hls.tcl -notrace
INFO: [HLS 200-10] Running '/opt/Xilinx/Vitis_HLS/2023.1/bin/unwrapped/lnx64.o/vitis_hls'
INFO: [HLS 200-10] For user 'phanium' on host 'localhost' (Linux_x86_64 version 6.4.3-arch1-1) on Mon Jul 17 12:17:34 CST 2023
INFO: [HLS 200-10] In directory '/home/phanium/xilinx/tmp/tmp'
INFO: [HLS 200-10] Bringing up Vitis HLS GUI ...
The hacking (https://wiki.archlinux.org/title/Xilinx_Vivado#Vitis_HLS_no_response_or_only_splash_screen_visible) don't work for me.
Potentially worth noting that Xilinx Information Center starts automatically with the installer (near the end of the "Installing files" phase), and adds a systray icon. Relevant documentation for disabling/uninstalling is at https://support.xilinx.com/s/article/59508.
/opt/Xilinx/Vivado/*/settings64.sh
invokes /opt/Xilinx/Vivado/2023.1/bin/setupEnv.sh
which outputs:
line 238: hostname: command not found
inetutils
seems to be a new dep.
Thanks for picking up the package Vitalyr!
I'm gonna orphan this since I have no desire to ever touch Vivado again and because packaging is getting increasingly tedious. If someone wants to pick it up and has questions, please feel free to contact me through IRC or matrix (@xiretza:xiretza.xyz).
As a completed information: I cost 16m11s and 21G to get vivado-2022.2-1-x86_64.pkg.tar.zst
. After installing, it costs 38.4G.
@ccorn: Thanks for your work.
I add a script to my PATH with the name arch
.
#!/bin/sh
uname -m
Start vitis works, but vitit_hls doesn't. I get this output, but nothing shows up.
INFO: [HLS 200-10] Bringing up Vitis HLS GUI ...
INFO: [HLS 200-112] Total CPU user time: 13.88 seconds. Total CPU system time: 0.96 seconds. Total elapsed time: 5.63 seconds; peak allocated memory: 98.906 MB.
INFO: [Common 17-206] Exiting vitis_hls at Mon Apr 10 05:11:43 2023...
I have tried patching the tcl file but only the output message had some change, and nothing shows up.
Those messages are normal. What did it install to ~/Downloads/
? That definitely shouldn't happen.
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
.