Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatible Version of GLIBC #466

Open
dragazo opened this issue Jan 4, 2025 · 3 comments
Open

Incompatible Version of GLIBC #466

dragazo opened this issue Jan 4, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@dragazo
Copy link

dragazo commented Jan 4, 2025

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 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:

$ LD_LIBRARY_PATH=/home/devin/glibc/glibc-2.34-install/lib /home/devin/.rustup/toolchains/esp/bin/cargo
Segmentation fault (core dumped)

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:

  1. Use a system with glibc 2.31 or below (mine is precisely 2.31)
  2. Run espup update
  3. Attempt to use 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

  • OS: Linux Mint 20
  • espup version: 0.14.0

Additional context

N/A

@dragazo dragazo added the bug Something isn't working label Jan 4, 2025
@github-project-automation github-project-automation bot moved this to Todo in esp-rs Jan 4, 2025
@SergioGasquez
Copy link
Member

Is there any reason not to update your OS? See esp-rs/rust-build#252

@dragazo
Copy link
Author

dragazo commented Jan 7, 2025

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.

@SergioGasquez
Copy link
Member

Glibc 2.35 should work fine afaik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

2 participants