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
Hi, I'm not sure exactly which repo to open this issue, but I'll start with espup since it's the updater for the esp toolchain.
About a year ago, I was using the esp toolchain (installed via espup) and everything was totally fine. However, I recently decided to get back into that project, so I did an espup update and opened up my project. When I try to build, or even use cargo for anything whatsoever, I get the following error:
/home/devin/.rustup/toolchains/esp/bin/cargo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/devin/.rustup/toolchains/esp/bin/cargo)
/home/devin/.rustup/toolchains/esp/bin/cargo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/devin/.rustup/toolchains/esp/bin/cargo)
/home/devin/.rustup/toolchains/esp/bin/cargo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/devin/.rustup/toolchains/esp/bin/cargo)
I can't really update glibc without obliterating my computer, but I did a side installation (from source) of glibc 2.34 and tried to use that:
If I do two system updates/migrations I could get to 2.35 (from 2.31), but based on the error message, that would actually be too high of a version to work.
Bug description
Hi, I'm not sure exactly which repo to open this issue, but I'll start with espup since it's the updater for the esp toolchain.
About a year ago, I was using the esp toolchain (installed via espup) and everything was totally fine. However, I recently decided to get back into that project, so I did an
espup update
and opened up my project. When I try to build, or even usecargo
for anything whatsoever, I get the following error:I can't really update glibc without obliterating my computer, but I did a side installation (from source) of glibc 2.34 and tried to use that:
I guess this means I can no longer use
espup
and have to instead build the toolchain from source? Is there any info on how to do this?To Reproduce
Steps to reproduce the behavior:
espup update
cargo +esp
Expected behavior
I expected espup to install a build for my current glibc (or else error out, rather than installing an incompatible one)
Screenshots
N/A (terminal snippets above)
Environment
Additional context
N/A
The text was updated successfully, but these errors were encountered: