AB
Using "core2" is a fallback that will work on very old machines. In your
case -- if this happens to be a more modern, uniform HPC system -- you
might want to use a different architecture. For example, if you're building
on the compute nodes, and never run on the front end, then the default
should already work for you. Otherwise, choosing "knl" as architecture
should also work (and would also make it impossible to run on the front
end).
-erik
On Thu, Oct 13, 2016 at 1:18 PM, ABB <austinb...@gmail.com> wrote:
> I built Julia Version 0.5.1-pre+2 on a cluster I have access to.
>
> The login node on which I executed the build has this architecture:
>
> Intel Core i7-5000 Extreme Edition (Haswell R2) / Xeon E5-x600 v3
> (Haswell-EP C1/M1/R2), 22nm
>
> The compute node has this architecture:
>
> Intel Xeon Phi Coprocessor (Knights Landing), 14nm
>
> (Those are each the last line of the output of "cpuid")
>
> when I try to run anything, I get the error:
>
> ERROR: Target architecture mismatch. Please delete or regenerate
> sys.{so,dll,dylib}.
>
> I found this old discussion:
>
> https://groups.google.com/forum/#!msg/julia-dev/Eqp0GhZWxME/3mGKX1l_L9gJ
>
> which recommends using
>
> JULIA_CPU_TARGET = core2
>
> in the Make.user file.
>
> Since that discussion is 2 years old, I am just double checking to see if
> that's still the best advice or if there is something else I should try
> first and/or instead.
>
> Thanks!
>
> AB
>
--
Erik Schnetter <schnet...@gmail.com>
http://www.perimeterinstitute.ca/personal/eschnetter/
