# How to compile Julia on cluster with slightly different login / compute nodes?

**URL:** <https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515>\
**Category:** General Usage\
**Created:** [October 30, 2019, 9:06pm UTC](https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515 "2019-10-30T21:06:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marius311](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marius311/32/3953_2.png) [@marius311](https://discourse.julialang.org/u/marius311)\
**Post date:** [October 30, 2019, 9:06pm UTC](https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515/1 "2019-10-30T21:06:44Z")

</div>

I’m on a cluster where I think the login / compute nodes are sufficiently different architectures that compiling Julia (1.3.0-rc4) on one and running on the either always yields a `ERROR: Unable to find compatible target in system image.` The prebuilt Julia executables from the website work fine, however. If I do want to compile my own versions though, can someone suggest what compile flags I might need? For reference, I attach a diff of the `/proc/cpuinfo` between the login/compute nodes. Thanks.

 ![image](https://global.discourse-cdn.com/julialang/original/3X/0/4/04c111ae2bb65a6079833bd02f74af15868bfebe.png)

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [October 30, 2019, 10:55pm UTC](https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515/2 "2019-10-30T22:55:10Z")

</div>

Not an expert but have you looked at [https://github.com/JuliaLang/julia/blob/master/doc/build/linux.md#architecture-customization](https://github.com/JuliaLang/julia/blob/master/doc/build/linux.md#architecture-customization) ?

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [October 30, 2019, 10:57pm UTC](https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515/3 "2019-10-30T22:57:55Z")

</div>

Are all of the compute nodes the same architecture?

If so, why not just compile Julia once on the compute nodes, and save the results. And then use that Julia every time you are running on the compute nodes.

---

<div class="post-metadata">

**Author:** ![marius311](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marius311/32/3953_2.png) [@marius311](https://discourse.julialang.org/u/marius311)\
**Post date:** [October 30, 2019, 11:27pm UTC](https://discourse.julialang.org/t/how-to-compile-julia-on-cluster-with-slightly-different-login-compute-nodes/30515/4 "2019-10-30T23:27:07Z")

</div>

Thanks. Based on that plus blindly taking a hint from [Use PackageCompiler to produce EXE on non-VM, execute on VM gives "ERROR: Unable to find compatible target in system image" - #2 by nodrygo](https://discourse.julialang.org/t/use-packagecompiler-to-produce-exe-on-non-vm-execute-on-vm-gives-error-unable-to-find-compatible-target-in-system-image/23521/2) it seems to be working with `MARCH=core2` in my `Make.user`. Not sure if there’s a better choice, will see if I see any noticeable slowdowns…