Cannot be used for older `glibc` libs

[farzadmf]

Hi,

I tried setting tea up in Amazon Linux 2 (which I think is using an older version of GLIBC), and I'm getting the following errors:

/home/farzadmf/.tea/tea.xyz/v*/bin/tea: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/farzadmf/.tea/tea.xyz/v*/bin/tea)
/home/farzadmf/.tea/tea.xyz/v*/bin/tea: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /home/farzadmf/.tea/tea.xyz/v*/bin/tea)
/home/farzadmf/.tea/tea.xyz/v*/bin/tea: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/farzadmf/.tea/tea.xyz/v*/bin/tea)

[jhheider]

I've been hammering away at trying to get glibc built so we can inject it if needed, but it's slow going.

#147

[farzadmf]

Thank you @jhheider for the quick reply.

While I have you here 🙂 , may I ask if tea is actually "production ready" or not.

I've been following tea for the past couple of months, and I'm heavily using Homebrew on my Mac and Linux. Is tea ready to replace my brew? (Of course, once the glibc issue is fixed 😆)

[jhheider]

The gui is currently in beta, and, while the CLI hasn't released v1 yet, it is used in all of our pipelines to build itself. However, as we haven't released v1, the public API is subject to change.

I would probably feel comfortable using tea in various production environments, but I'm sure there's plenty of people who would advocate waiting for v1.

[farzadmf]

Great, thanks for letting me know. Hopefully, the glibc issue is fixed soon and I can take this for a ride

The GUI also is/will be cross-platform?

[jhheider]

Yup, the plan is for tea to be everywhere.

[mxcl]

I'd say tea/cli is pretty mature; as jacob says we use it all over the place. But it cannot compete with brew’s maturity, brew is 14 years old.

tea can do things brew cannot, so I would use it there. You may have issues, but we are finding less and less of those each day. So go into it knowing that. Thanks for being part of this!

[mxcl]

@jhheider amazon linux 2 requiring glibc 27 while we go back to 28 is possibly reason enough for us to try and build against 27.

[jhheider]

We could try and base off an aml minimal image. Worth testing.

[tannevaled]

FYI — pantry now ships gnu.org/glibc as a multi-version recipe (#12968, merged 2026-05-22) covering 9 glibc versions × 2 arches including the HPC-era 2.17 / 2.24 and intermediate 2.26 / 2.27 / 2.28 etc. That gives pantry recipes the ability to target older glibc levels — useful when packaging tools meant to run on Amazon Linux 2 / RHEL 7 / SLES 12 hosts.

The original symptom you reported is the pkgx core binary itself failing to load on AL2 (which ships glibc 2.26). That's still a pkgx-core distribution question (the pkgx binary needs to be built against a baseline-compatible glibc, or shipped multi-arch). Not pantry-side.

If the original blocker was "I want my pantry-installed tools to work on AL2," the glibc recipe + brewkit's bottle-relocation work (brewkit#348 + brewkit-bottle-relocation pattern) gets you most of the way. If it's "I want to run pkgx itself on AL2," that needs to move to pkgxdev/pkgx.