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

ygen install broken #1481

Open
mattgodbolt opened this issue Dec 12, 2024 · 4 comments
Open

ygen install broken #1481

mattgodbolt opened this issue Dec 12, 2024 · 4 comments

Comments

@mattgodbolt
Copy link
Member

Can't run:

2024-12-12 15:01:30,250 lib.installation_context INFO     Removing temporarily moved /opt/compiler-explorer/staging/09b6aa4b-a19c-4d7d-85f7-eae954c7ae28.orig
/opt/compiler-explorer/ygen/bin/ylc: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /opt/compiler-explorer/ygen/bin/ylc)
2024-12-12 15:01:30,533 lib.ce_install  ERROR    compilers/ygen/ylc newest installed OK, but doesn't appear as installed after

it's built with a newer gcc than our system has access to.

cc @Cr0a3

@Cr0a3
Copy link
Contributor

Cr0a3 commented Dec 12, 2024

Can't run:

2024-12-12 15:01:30,250 lib.installation_context INFO     Removing temporarily moved /opt/compiler-explorer/staging/09b6aa4b-a19c-4d7d-85f7-eae954c7ae28.orig
/opt/compiler-explorer/ygen/bin/ylc: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /opt/compiler-explorer/ygen/bin/ylc)
2024-12-12 15:01:30,533 lib.ce_install  ERROR    compilers/ygen/ylc newest installed OK, but doesn't appear as installed after

it's built with a newer gcc than our system has access to.

cc @Cr0a3

Hmm sorry 🤔.
I'll rerun the release build artifact workflow for my project. Maybe it is then fixed. Else I would need to downgrade my dependencies versions

@mattgodbolt
Copy link
Member Author

I'll rerun the release build artifact workflow for my project. Maybe it is then fixed.

I can't see how it could possibly fix itself. I imagine you've updated the ubuntu build (or are using a Github tagged image that updated).

Let me know though when you've got a new build and I can test it.

@Cr0a3
Copy link
Contributor

Cr0a3 commented Dec 13, 2024

I'll rerun the release build artifact workflow for my project. Maybe it is then fixed.

I can't see how it could possibly fix itself. I imagine you've updated the ubuntu build (or are using a Github tagged image that updated).

Let me know though when you've got a new build and I can test it.

There should be a new build online

@mattgodbolt
Copy link
Member Author

Unsurprisingly building it again hasn't caused it to use an older glibc:

$ objdump -T /opt/compiler-explorer/ygen/bin/ylc | grep -Eo 'GLIBC_\S+' | sort -u
GLIBC_2.14)
GLIBC_2.16)
GLIBC_2.18)
GLIBC_2.2.5)
GLIBC_2.25)
GLIBC_2.28)
GLIBC_2.3)
GLIBC_2.32)
GLIBC_2.33)
GLIBC_2.3.4)
GLIBC_2.34)
GLIBC_2.38)

it's still linking against glibc 2.38 which is from 2023 https://sourceware.org/glibc/wiki/Glibc%20Timeline and is not in the Ubuntu 22.04 images we use.

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

No branches or pull requests

2 participants