You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMPORTANT
Please read README and Docs before creating the issue.
Please fill out the below information: Describe the issue
I haven't used ArchWSL in a couple months, but I notice I was having upgrade issues complaining about lib32-glibc when upgrading so I had to use lib32-glibc-linux4 from the archlinuxcn repo.
This was on a new install.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Enviroment:
Windows build number: [e.g. 10.0.17134.228] (Type ver at a Command Prompt)
Security Software: [e.g. ESET Internet Security]
WSL version 1/2: [e.g. WSL1]
ArchWSL version [e.g. 19.3.7.0]
ArchWSL Installer type zip/appx/other clean/update [e.g. appx update]
Launcher version [e.g. 19030700] (Type Arch.exe version at a Command Prompt)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
As the maintainer of glibc-linux4 said in [https://aur.archlinux.org/packages/glibc-linux4#comment-930385]
The normal glibc v2.38 works perfectly fine with WSL 1, which is on Linux v4.4.0. There is no need to update & use glibc-linux4 at the moment AFAIK.
If you do need glibc-linux4 v2.38 as normal glibc will not work for you, please be sure to provide the details when you flag this package.
You'd better install official package to replace glibc-linux4 and lib32-glibc-linux4
IMPORTANT
Please read README and Docs before creating the issue.
Please fill out the below information:
Describe the issue
I haven't used ArchWSL in a couple months, but I notice I was having upgrade issues complaining about lib32-glibc when upgrading so I had to use lib32-glibc-linux4 from the archlinuxcn repo.
This was on a new install.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Enviroment:
ver
at a Command Prompt)Arch.exe version
at a Command Prompt)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: