Puppy Linux Discussion Forum

@ozs outh:-

Yes, I did it in bionicpup64. The procedure, I think, is suitable for bionicpup64. For fossapup64, I found the the glibc contents are not stored neither in /usr/lib nor /lib. It
stores in /lib/x86_64-linux-gnu. According to your glibc compilation config, The final contents of the glibc ...

In long term run, probably the glibc has to be upgraded because the applications may need the new version of glibc.
For example, I run the bionicpup64, the browser palemoon new version requires the new glibc. That my reason to upgrade the glibc.
Now my bioinicpup64 is running with glibc version 2.40 ...

I have successfully upgrade the glibc.
The procedure is as follow:
Assume the installed puppy is in frugal installation (I called it as Puppy-A)

The procedure:

1. Compile new version of glibc with –prefix=/
2. Do not install to the live system. Instead install to another folder say newver-glibc ...