Glibc 2.41 introduced a breaking change where it won't load .so files flagged with execstack without some extra configuration. The Julia build process includes a line in a makefile that (I think) forces libopenlibm.so to be built without the execstack flag due to this problem. However, the standalone build process for openlibm does not seem to include such a flag.
The libopenlibm4 0.8.1 package on conda-forge is built with execstack, which means Julia won't run in a conda environment on Fedora linux. (Fedora 43 enables SELinux, checks for execstack, and uses glibc 2.42.) I suspect the conda package is built exactly as posted here on github.
Can you add that noexecstack flag to the build process?
Glibc 2.41 introduced a breaking change where it won't load .so files flagged with execstack without some extra configuration. The Julia build process includes a line in a makefile that (I think) forces libopenlibm.so to be built without the execstack flag due to this problem. However, the standalone build process for openlibm does not seem to include such a flag.
The libopenlibm4 0.8.1 package on conda-forge is built with execstack, which means Julia won't run in a conda environment on Fedora linux. (Fedora 43 enables SELinux, checks for execstack, and uses glibc 2.42.) I suspect the conda package is built exactly as posted here on github.
Can you add that noexecstack flag to the build process?