[email protected] 2.17 (new formula)

[ZhongRuoyu]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

This is part of the effort to bring Portable Ruby (and perhaps Homebrew) to AArch64 Linux.

2.17 is the first glibc version that supports AArch64 ¹. As discussed previously ², this formula will allow us to later build Portable Ruby against this version of glibc for maximum coverage of Linux distributions on AArch64.

Footnotes

1. https://sourceware.org/glibc/wiki/Release/2.17 ↩

2. https://github.com/Homebrew/homebrew-portable-ruby/pull/212 ↩

[Bo98]

Looks good but making sure unversioned glibc works in aarch64 is required for us to use this so worth checking that it does (the bootstrap stuff can however come later).

[ZhongRuoyu]

making sure unversioned glibc works in aarch64 is required for us to use this so worth checking that it does

Since we don't really have any aarch64 Linux bottles, is there anything that we should test in particular? I did conduct some very basic testing, and I can do more some more extensive ones later.

With binaries from Homebrew/glibc-bootstrap#31, I bootstrapped the unversioned glibc 2.35 on CentOS 7 (system glibc version 2.17), and tested a handful of bottles there (hello, xz, gzip, ...), that were built on another Ubuntu 22.04 system with system glibc 2.35.

I haven't tested building formulae from source yet as I had to first build GCC and all its dependencies from source which was a bit too heavy for a quick test in Docker on a Raspberry Pi. (For the same reason I used --ignore-dependencies to install the bottles.)

[Bo98]

Since we don't really have any aarch64 Linux bottles, is there anything that we should test in particular? I did conduct some very basic testing, and I can do more some more extensive ones later.

With binaries from Homebrew/glibc-bootstrap#31, I bootstrapped the unversioned glibc 2.35 on CentOS 7 (system glibc version 2.17), and tested a handful of bottles there (hello, xz, gzip, ...), that were built on another Ubuntu 22.04 system with system glibc 2.35.

That test seems fine to me. If glibc builds fine and is usable then that sounds good to me.

[github-actions]

@p-linnane has requested bottles to be published to this PR.