Bazel and Glibc Versions
14 comments
·September 20, 2025fooblaster
lokar
Yeah, making the entire tool chain hermetic and versioned is one of the main benefits of bazel.
You can have every developer cross-compile from a different os/cpu platform
jmmv
Because those Bazel toolchains don’t come with a glibc? How could they?
paulddraper
Agreed.
notpushkin
> the service crashes with a mysterious error: version 'GLIBC_2.28' not found
Mysterious?
This is by the way why many binary Python packages use https://github.com/pypa/manylinux for builds: if you build on an old glibc, your library will still (generally) work with newer versions.
shykes
It appears the Bazel community is getting closer to inventing containers.
jeffbee
Bazel comes with ironclad sandboxing features, but people don't use them because build correctness is such a chore.
null
paulddraper
Bazel has number of strategies, including containers.
But that’s only a minority of what it does.
Why ain't the first answer.. use a bazel provided tool chain instead of using system toolchains? This article is totally mad.