-
Notifications
You must be signed in to change notification settings - Fork 757
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
[sw, bazel] Compilation of uart_smoketest fails #18993
Comments
I was able to narrow the problem down a bit by manually executing the failing command in the respective directory. Then, the error I get is
The problem seems to be somewhere internally in Bazels build directory structure. When I do
I get
but not the request |
Any chance you are using NFS for bazel's outputs? bazel would have warned that this leads to surprising failures. |
Thanks for the hint towards NFS directories. This was indeed the case in the beginning, but after figuring out how to change the output directory via Additionally, I switched from CentOS 7 to Alma Linux 8, again with no success. The issue above seems to be resolved by deleting the output directory and rebuilding from scratch, not exactly sure how. Now I am stuck at
which I guess is a result from |
Yes, missing opentitan/yum-requirements.txt Line 45 in 43ad38b
If you're back to Alma Linux 8, you'll have to roll your own installation of that, since the package wasn't built for EPEL 8. One option would be to build the RPM yourself (assumes you have rpmdevtools and all the dependencies for the package build installed): # Get the srecord build from Fedora
git clone https://src.fedoraproject.org/rpms/srecord.git
# Download the sources
spectool -g -R srecord/srecord.spec
# Build the RPM
rpmbuild -bb srecord/srecord.spec
# Install the RPM (actual path may depend on where your RPM dev tree is--I forget)
dnf localinstall -y ./rpmbuild/RPMS/x86_64/srecord-1.64-24.el8.x86_64.rpm We use |
Thanks for the clarification of Additionally, I had to manually re-
So, using my updated Thanks for the help! |
Description
When trying to run to uart_smoketest as per the Getting Started command, after (quite) a while I get the following, similar errors:
I already added the
--sandbox_debug
toggle but honestly can't make much sense out of the error messages above. Any help would be greatly appreciated.The text was updated successfully, but these errors were encountered: