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

[help with downstream issue] Symbolic linking of libstdc++ broken #55

Open
tibotiber opened this issue Jan 11, 2022 · 3 comments
Open

Comments

@tibotiber
Copy link

Hello!

After the last update, we've been seeing some issues with the installation of libstdc++. See report in the downstream repo: tibotiber/hasura-action#13.

2022-01-10T07:32:02.0266519Z �/usr/glibc-compat/sbin/ldconfig: /usr/glibc-compat/lib/ld-linux-x86-64.so.2 is not a symbolic link

I'm now explicitly using the previous version (for now) but I was wondering if you had any recommendation on how to get around this?

Cc @danisevas

@danisevas
Copy link
Contributor

@tibotiber This might be related to sgerrand/alpine-pkg-glibc#167
Maybe one of the solutions in the discussion will solve the problem for you.
In my setup, with the latest image (alpine3.15 glibc-2.34) I'm able to install libstdc++ with no problem.

@frol
Copy link
Member

frol commented Jan 11, 2022

Without a minimal reproducible example, I cannot do anything at all. I suggest you try to play with making that file a symlink, and try creating /usr/glibc-compat/lib/ld-2.34.so file (just copy ld-linux-x86-64.so.2 to it). Alternatively, you will need to debug things further and understand what makes a difference for it and why it suddenly requires the file to be a symlink (it was not a symlink in glibc-2.33 either, so I don't know what has changed)

@tibotiber
Copy link
Author

Thanks both for the answers. I'll have a look at what I can do with the suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants