Hi, Laurent Gatto <laurent.ga...@gmail.com> writes:
> Hi Fredrik, > >> So something else must be affecting yours. No idea about what that is >> though. Did you install guix as a package manager on top of an foreign >> distro or is this a Guix System machine? > > I should have specified that this is a Guix system machine. > >> Also has this ever worked for you? > > I am not sure, to be honest. Here, I tried to report a minimally > reproducible example of wider issues, such as documented here [1]. I > don't know if they are directly related though. > > [1] https://lists.gnu.org/archive/html/help-guix/2024-08/msg00040.html > I don't think these two are directly related. That one should work if you are using glibc-2.35. As the GLIBC_2.34 is just a symbol version for things introduced in glibc-2.34 and should be in glibc-2.35. I haven't fully understand how glibc is setup in guix, i.e. if it is easy to run multiple glibc versions at the same time. So the issue might be that your system is setup for glibc-2.33 but the packages have just transitioned to 2.35. I had some similar issues with glibc and pam which resolved itself after I did a reconfigure. >> If so you might trying doing a kind >> of git bisect on your packages using `guix package --switch-generation`. >> >> First find a working generation with `guix package --list-generations`, >> pick the generation that is in the middle of the latest broken >> generation and the older working one. Switch to that, do the test. If >> it works then the problem is most likely between that generation and the >> latest broken generation. If not, then the issue is between the current >> generation and the older working one. Pick the middle generation >> between the working and broken generation and repeat. >> >> Just keep iterating until you find the generation that introduced the >> issue. Then you can compare with the previous working generation to see >> if there are any differences in packages. > > I will try this. If push comes to shove, I could re-install a new Guix > system, reinstall my packages from my manifest and re-configure my > system and home config. This is among the reasons that brought me to > Guix in the first place, so why not make use of it. One great thing with guix is that you technically do not need to re-install a new guix system from scratch. You could create an absolute bare minimum system and reconfigure to that. Same with you packages. That should give you close to what is possible to a clean re-install without the hassel of do a clean re-install. And with that you can easily switch back to your normal config with switch-generations when you are done. Which is a similar technique to the generation bisect I suggested earlier. Which now that I think of it might be a better way to go for you as you are not sure if you had a working generation. Same principle as with the generations, but this time you apply it to all of your packages installed. Easiest if you have a manifest/home config etc. Just comment out all packages so you only have gcc-toolchain installed. See if that works, which it most likely will given that it works in the guix shell container. Then enable half of your packages, reconfigure and see if things still work. If it does, the issue is not in the packages you enable but in the other half. Enable that and repeat. If things are now broken then you know the issue is in some of the packages you enabled. So comment out a half of that and repeat. > Thanks again for taking the time to help. No worries, I hope you can figure out what the issue is. -- s/Fred[re]+i[ck]+/Fredrik/g
