# Help to use \`JuliaC\` on Centos7

**URL:** <https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961>\
**Category:** General Usage\
**Tags:** juliac\
**Created:** [January 9, 2026, 11:03am UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961 "2026-01-09T11:03:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmxam](https://avatars.discourse-cdn.com/v4/letter/b/b38774/32.png) [@bmxam](https://discourse.julialang.org/u/bmxam)\
**Post date:** [January 9, 2026, 11:03am UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961/1 "2026-01-09T11:03:42Z")

</div>

Hi everyone,

I’m trying to compile a julia script (just a simple helloworld, like in the JuliaC repo) using `JuliaC` on a Centos7 machine. I know Centos7 is EOL, but this is a constraint for an old HPC cluster.

As far as I know, the main constraint with Centos7 is the GLIBC version : 2.17.

What I’ve tried so far (using Docker images):

- centos:7 + download julia 1.12.4 + `app add JuliaC` + `juliac (...)`
- centos7-gcc13 + git clone julia (v1.12.4) + compile (USE\_BINARYBUILDER=1) + `app add JuliaC` + `juliac (...)`
- centos7-gcc13 + git clone julia (v1.12.4) + compile (USE\_BINARYBUILDER=0) + `app add JuliaC` + `juliac (...)`

juliac manages to compile an executable, but when I try to run this executable, the following error is raised:

```bash
error: runtime auto-initialization failed due to bad sysimage lookup
       (this should not happen, please file a bug report)

```

Do you have any clue on how to solve this? Is it even possible (with the constraint GLIBC = 2.17)?

Thank you!

---

<div class="post-metadata">

**Author:** ![langestefan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/langestefan/32/207923_2.png) [@langestefan](https://discourse.julialang.org/u/langestefan)\
**Post date:** [January 9, 2026, 11:25am UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961/2 "2026-01-09T11:25:52Z")

</div>

Probably best to file bug report like the error message suggests: [GitHub · Where software is built](https://github.com/JuliaLang/JuliaC.jl/issues)

---

<div class="post-metadata">

**Author:** ![bmxam](https://avatars.discourse-cdn.com/v4/letter/b/b38774/32.png) [@bmxam](https://discourse.julialang.org/u/bmxam)\
**Post date:** [January 9, 2026, 12:46pm UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961/3 "2026-01-09T12:46:19Z")

</div>

I’ve hesitated (like always) between an issue on repo or a message here, thinking that it was may be a dumb error. I’ve followed your advice and just posted an issue : [Using `JuliaC` on Centos7 · Issue #105 · JuliaLang/JuliaC.jl · GitHub](https://github.com/JuliaLang/JuliaC.jl/issues/105).

---

<div class="post-metadata">

**Author:** ![langestefan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/langestefan/32/207923_2.png) [@langestefan](https://discourse.julialang.org/u/langestefan)\
**Post date:** [January 9, 2026, 12:58pm UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961/4 "2026-01-09T12:58:24Z")

</div>

Atlernatively you could just run JuliaC on your local PC and then move the artifacts onto the HPC cluster.

---

<div class="post-metadata">

**Author:** ![bmxam](https://avatars.discourse-cdn.com/v4/letter/b/b38774/32.png) [@bmxam](https://discourse.julialang.org/u/bmxam)\
**Post date:** [January 9, 2026, 7:57pm UTC](https://discourse.julialang.org/t/help-to-use-juliac-on-centos7/134961/5 "2026-01-09T19:57:39Z")

</div>

I am afraid I can’t do that : on my local PC the binary will be “bind” (sorry for the vocabulary, I’m not an expert at all) with GLIBC\_2.34, which does not exist on centos:7. I just did the test : I compiled a (working) helloworld on ubuntu:latest, moved it to centos:7 and obtained

```julia-auto
/compiled/bin/app_test_exe: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /compiled/bin/app_test_exe)

```