-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vitis_setup.sh with non-root permissions #618
Comments
Dear customer You need sudo permissions if you do not have all the required packages referred to in vitis_setup.sh script, to install the required packages. Did you verify that all the packages are available in your environment? Thanks |
Yes, the packages required by the script are satisfied and the script has been sourced by root once already on this system. When running without root/sudo permissions:
|
Dear customer You might be seeing those errors because the script tries to install the required packages which require root permissions by default. You need to manually disable those install steps that are trying to install the packages required. However please make sure you have the exact packages with the exact versions the script tries to install or else might see other issues with further development steps Please feel free to let us know if you have any follow up questions Thanks |
It looks like the main issue is actually in the sdk_setup.sh that is called by the vitis_setup.sh file. Lines 33-40 are setting explicit root permissions on a file in /tmp, is this required to be owned and created by the root user? Does the sdk_root_env.exp file need to be writable by any user that is going to be running this vitis_setup.sh?
|
Running as non-root:
Running as root:
|
We are attempting to run the vitis_setup.sh script in a managed environment which already has all of the pre-reqs (Vivado, Vitis, python, etc) installed and available, but we don't have root access to the host.
Is there an alternative way to source this vitis_setup.sh script without the requirement for root level access?
The text was updated successfully, but these errors were encountered: