Skip to content
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

Updated Verilator to not reply on system python #288

Merged
merged 1 commit into from
Mar 3, 2024

Conversation

abrisco
Copy link
Collaborator

@abrisco abrisco commented Mar 2, 2024

In my remote executor image I explicitly don't want python/python3 to appear on PATH and to instead rely on toolchains defined in Bazel to correctly match an interpreter. I noticed there were some genrules when building Verilator that were relying on this behavior. I've replaced the genrules used by Verilator with proper rules and py_binary targets to make builds more hermetic.

@abrisco abrisco force-pushed the verilator branch 7 times, most recently from 4b7c430 to 99ca8ea Compare March 2, 2024 19:10
@QuantamHD
Copy link
Collaborator

Running CI. Thanks for the contribution

@QuantamHD
Copy link
Collaborator

/gcbrun

@QuantamHD
Copy link
Collaborator

Can you resolve the merge conflict. Otherwise looks good

@abrisco
Copy link
Collaborator Author

abrisco commented Mar 2, 2024

@QuantamHD rebased!

@QuantamHD
Copy link
Collaborator

/gcbrun

@abrisco
Copy link
Collaborator Author

abrisco commented Mar 3, 2024

@QuantamHD Looks like CI is passing 😃

@QuantamHD QuantamHD merged commit ea302c2 into hdl:main Mar 3, 2024
4 checks passed
@abrisco abrisco deleted the verilator branch March 3, 2024 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants