-
Notifications
You must be signed in to change notification settings - Fork 7
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
Failure compiling MRI #44
Comments
What Linux distro is that? |
Ubuntu 20.04.6 LTS
|
I tried installing using bare Ubuntu 20.04 Docker image and it worked fine: $ docker run --platform=linux/amd64 -v $(pwd):/rules_ruby -ti ubuntu:20.04 bash $ uname -a
Linux 6d3c0a69477d 6.4.16-linuxkit #1 SMP PREEMPT Wed Oct 25 16:32:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
# Bazelisk
$ apt-get update -y && apt-get install -y wget && wget https://github.com/bazelbuild/bazelisk/releases/download/v1.19.0/bazelisk-linux-amd64 -O /usr/local/bin/bazel && chmod +x /usr/local/bin/bazel
# Ruby deps
$ apt-get install -y build-essential libz-dev libyaml-dev perl
$ cd /rules_ruby/examples/gem
$ echo "3.0.6" > .ruby-version
$ RUBY_RULES_DEBUG=1 bazel build ...
...
INFO: Build completed successfully, 31 total actions Shall I use some other Docker image to try and reproduce? |
I imagine you'd want an image that already has ruby installed on the system. |
I've installed Ruby 2.7 using apt-get and still could get the toolchain to install w/o problems. How did you install your Ruby? |
I have no idea, maybe with the system or from some transitive effect of If we can't reproduce then let's wait to see if users report it? |
Have you seen something like this?
This error feels to me like the repository rule is trying to write to some global location on my disk, and maybe we need to set an environment variable like
XRUBY_RUBYLIBDIR
somewhere so the MRI build process is okay with running in some read-only sandbox?I'm on Linux, tried ruby 3.0.6 and 3.2.2, get an error like the following
I do have a system ruby already
The text was updated successfully, but these errors were encountered: