On Mon, Jan 17, 2022 at 12:57:54PM +0100, Ricardo Wurmus wrote:
>
> jsmith via <help-guix@gnu.org> writes:
>
> > ERROR: In procedure dlopen:
> > In procedure dlopen: file
> > "/gnu/store/35apwp40n8rnlqyxf7hagwr250nw754w-guile-dbi-2.1.8/lib/libguile-dbi.so",
> > message
> > "/gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6:
> > version `GLIBC_2.33' not found (required by
> > /gnu/store/z0kk97dcbcj6s8crm3qiwsyz4ry0zqxw-guile-2.2.7/lib/libguile-2.2.so.1)"

Hey, this sounds just like the problem I reported earlier this month.

   /gnu/store/bb27inmp90vyx59q1453zl1rs9h73kjd-guile-wrapper/bin/guile: /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/3lsrx30nl5cacva8a8rd2xy08xlszx14-libx11-1.7.2/lib/libX11.so.6)
   /gnu/store/bb27inmp90vyx59q1453zl1rs9h73kjd-guile-wrapper/bin/guile: /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/2sgw9si0va897m6mvgwmv9ilx6szqxc8-libxau-1.0.9/lib/libXau.so.6)
   /gnu/store/bb27inmp90vyx59q1453zl1rs9h73kjd-guile-wrapper/bin/guile: /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/7x63qm1byi8j72rd4nkv01nbpqvrr80s-libbsd-0.10.0/lib/libbsd.so.0)

> The problem you describe looks like you have a mixture of packages that
> have been linked with different versions of the GNU C library, which
> indicates that you used different versions of Guix to build/install
> them.

Is this possible at all? Aren’t builds atomic, and isn’t guix version
change considered an input change, so that builds by various guix
versions are prevented by design from being mixed while linking?

> Here an older version of the C library is loaded first because some
> package you have is linked with that older version.

Again, could it be a system-wide version: the system build with guix X,
guix upgraded to X+1, user package built with guix X+1, while the system
is still at guix X, so that the package links to system-wide libc build
with guix X?

> a) use a manifest to ensure that all packages in your profile are
> installed with the exact same version of Guix and thus use the same
> variants for all libraries

> c) use a temporary isolated environment, e.g. with “guix shell -C”

My bug is produced when I use a manifest and an isolated environment. I
also discovered that I’m getting the same errors while loading profiles.
Rebuilding profiles (with a newer guix as they’re not time-machined with
some exceptions) fixes this.

WŻ