Use static link for compare scripts #3196
Conversation
In case you have different GLIBC versions inside and outside of the chroot we would get errors. As dynamic linking saves a bit of space we shouldn't always do this but as we only do this for compare scripts and not the submissions this is quite a small diskoverhead.
|
I have to think through this, just leaving a reference to #2162 here in case someone is interested in the larger issue |
|
I tried this when running into it at our BAPC preliminary and it wasn't working. I don't remember the exact reason anymore though. One possible reason: IIRC not all Linux distributions provide static link libraries. |
|
Jaap, what distro did you use? |
Host distro CentOS 9, chroot using Debian Bookworm (oldstable) I think, but could have been Trixie (stable). |
FYI, I'm now referring to this year's setup. In #2162 that was an older setup with CentOS 8 in 2023. Actually, this year, I think I fell back to Bookworm because that had a compatible GLIBC, while Trixie didn't and I didn't get that to work, including with using static compilation. |
|
Just for reference, these are the diffs from my attempts to make it work. I need to dive a bit deeper to find out what actually failed for what reasons. |
3 participants
In case you have different GLIBC versions inside and outside of the chroot we would get errors. As dynamic linking saves a bit of space we shouldn't always do this but as we only do this for compare scripts and not the submissions this is quite a small diskoverhead.
We already have an issue to fix this in a proper way but as I encountered this both for alpine and in my laptop install (which is quite outdated with 22.04) I do think this is a good temporary fix.