Search Criteria
Package Details: ruby-build 20241105-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ruby-build.git (read-only, click to copy) |
---|---|
Package Base: | ruby-build |
Description: | Compile and install Ruby |
Upstream URL: | https://github.com/rbenv/ruby-build |
Licenses: | MIT |
Submitter: | None |
Maintainer: | saghm |
Last Packager: | saghm |
Votes: | 101 |
Popularity: | 0.62 |
First Submitted: | 2011-12-26 13:37 (UTC) |
Last Updated: | 2024-11-05 09:07 (UTC) |
Dependencies (3)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR)
- git (git-gitAUR, git-glAUR) (optional) – install ruby from git
- libyaml (libyaml-gitAUR) (optional) – install recent versions of mri
Required by (3)
- rbenv (optional)
- rbenv-git (optional)
- rbenv-vagrant-setup-git
Latest Comments
1 2 3 4 5 Next › Last »
saghm commented on 2023-01-24 04:02 (UTC)
From looking into this, it seems like most of the other versions of Ruby besides mri (e.g. jruby and truffleruby) still install fine without libyaml. These all report versions below 3.2.0 when invoking
ruby -v
though, so it's possible that they might break without this in the future.For now, I'm thinking that I should add it as an optional dependency and mention that it's required for recent versions of mri.
saghm commented on 2023-01-23 22:21 (UTC)
Interesting! Let me look into this and confirm before adding it (but I suspect you're correct)
synthead commented on 2023-01-23 03:33 (UTC)
Ruby 3.2.0 doesn't build (and probably run) without libyaml. This probably affects other versions, too. Can you add it as a dep?
nyi commented on 2022-11-07 10:37 (UTC)
Not so sure if this is the right place, but it might help someone struggling with failing Ruby builds due to the openssl extension.
I got the following now:
It seems Ruby doesn't work with OpenSSL 3 yet. Install
core/openssl-1.1
and then install Ruby as:just1602 commented on 2020-12-25 21:30 (UTC)
Here the diff you need to apply if you want the latest version and try ruby 3.0.0:
saghm commented on 2020-09-29 17:30 (UTC)
Sorry about the issue! I've pushed a new version that should now be working; let me know if it doesn't
whi-tw commented on 2020-09-29 11:18 (UTC) (edited on 2020-09-29 11:18 (UTC) by whi-tw)
Confirmed working with the same solution as @nyi:
Xanarion commented on 2020-09-29 08:20 (UTC) (edited on 2020-09-29 08:20 (UTC) by Xanarion)
I don't understand how this would unless you change the
build()
section to:If you don't make the change above - you get the error that states:
nyi commented on 2020-09-29 08:15 (UTC)
The downloaded file is now called
v20200926.tar.gz
instead ofruby-build-v20200926.tar.gz
.You can fix the build by changing the following line in
PKGBUILD
:kfl62 commented on 2020-09-29 05:18 (UTC)
==> Starting build()... tar (child): ruby-build-v20200926.tar.gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ==> ERROR: A failure occurred in build(). Aborting... error making: ruby-build
1 2 3 4 5 Next › Last »