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

dealing with the glibc dependency #233

Open
johnynek opened this issue Jan 3, 2024 · 1 comment
Open

dealing with the glibc dependency #233

johnynek opened this issue Jan 3, 2024 · 1 comment
Assignees
Labels
bug Something isn't working hermeticity Issues dealing with compiler hermeticity
Milestone

Comments

@johnynek
Copy link
Collaborator

johnynek commented Jan 3, 2024

We got burned one more time with a graal image being cached, but built on a machine running a different version of glibc. So a trick occurred to me that I implemented here:

andyscott/rules_graal#24

the idea is to include as a resource a hash (or some information) that depends on the glibc version. So, when that changes, it automatically busts the hash.

I had to revert to using the old graalvm rules because I couldn't get our repo to work with these in the time I had set aside, but I thought I would share this approach if anyone wants to implement it for these rules.

So far, this has prevented any issues we've seen when some of our builds are on different versions of ubuntu.

@sgammon
Copy link
Owner

sgammon commented Jan 3, 2024

@johnynek Hey, happy 2024. Thanks for reporting. I've got a new release waiting in the wings so I can get a fix in on this quickly.

@sgammon sgammon added bug Something isn't working hermeticity Issues dealing with compiler hermeticity labels Jan 8, 2024
@sgammon sgammon self-assigned this Jan 8, 2024
@sgammon sgammon added this to the 1.0.0 milestone Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working hermeticity Issues dealing with compiler hermeticity
Projects
Development

No branches or pull requests

2 participants