# Will juliac solve the relocatabiliy issue?

**URL:** <https://discourse.julialang.org/t/will-juliac-solve-the-relocatabiliy-issue/131780>\
**Category:** General Usage\
**Tags:** question\
**Created:** [August 22, 2025, 7:35pm UTC](https://discourse.julialang.org/t/will-juliac-solve-the-relocatabiliy-issue/131780 "2025-08-22T19:35:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ohmsweetohm1](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ohmsweetohm1/32/49126_2.png) [@ohmsweetohm1](https://discourse.julialang.org/u/ohmsweetohm1)\
**Post date:** [August 22, 2025, 8:01pm UTC](https://discourse.julialang.org/t/will-juliac-solve-the-relocatabiliy-issue/131780/3 "2025-08-22T20:01:49Z")

</div>

> [@ufechner7](#):
>
> To the best of my knowledge this is an un-related problem that can be solved separately.

Unrelated to what? Isn’t the goal of juliac to build standalone executables?

> [@Julia slower than Python for finding pangrams?](https://discourse.julialang.org/t/julia-slower-than-python-for-finding-pangrams/112481/8):
>
> The good news is that we’re getting closer to having a real `juliac` that can output compiled stand-alone executables with significantly lower startup times like `cc` does.

The usefulness is very limited if they are not relocatable.

---

_[View the full topic](https://discourse.julialang.org/t/will-juliac-solve-the-relocatabiliy-issue/131780)._