Julia release fails to launch do to invalid library argument

[theplatters]

Whenever I try to start julia (current release 1.11.3) i get the following error:

ERROR: Unable to load dependent library /home/franzs/.julia/juliaup/julia-1.11.3+0.x64.linux.gnu/bin/../lib/julia/libopenlibm.so
Message:/home/franzs/.julia/juliaup/julia-1.11.3+0.x64.linux.gnu/bin/../lib/julia/libopenlibm.so: cannot enable executable stack as shared object requires: Invalid argument

I am using Juliaup 1.17.11 installed through the AUR.

[theplatters]

I made it work by executing:

execstack -c /home/franzs/.julia/juliaup/julia-1.11.3+0.x64.linux.gnu/lib/julia/libopenlibm.so

apparently the stack is incorrectly marked as executable.

[theplatters]

The problem is not present, when I install Julia through the official arch repository

[fjebaker]

I get the same error. The above execstack command worked for me too. I also used it to query all of the shared object files and it's only libopenlibm.so that has the executable stack flag set.

[KristofferC]

See JuliaLang/julia#57250

[divital-coder]

Juliaup is broken based on this bug for Julia versions above 1.8, all Julia version 1.9, 1.10, 1.11 are resulting in the aforementioned error.

[StefanKarpinski]

TLDR: Juliaup is not broken, nor are the older Julia versions that this affects. Rather, glibc made a breaking release (which is bonkers) and it broke a lot of software, including older releases of Julia, which worked fine before. We're working through the best way to address the situation but making an actual new release of dozens of old releases that we can't even run CI for anymore is not straightforward.

[KristofferC]

versions above 1.8, all Julia version 1.9, 1.10, 1.11 are resulting in the aforementioned error.

1.10 and 1.11 should be fixed now.

[divital-coder]

TLDR: Juliaup is not broken, nor are the older Julia versions that this affects. Rather, glibc made a breaking release (which is bonkers) and it broke a lot of software, including older releases of Julia, which worked fine before. We're working through the best way to address the situation but making an actual new release of dozens of old releases that we can't even run CI for anymore is not straightforward.

Wow, even glibc folks push breaking changes?? Bonkers, Indeed