I think this is the actual error:
/home1/04179/abean/julia/deps/srccache/llvm-svn/lib/Demangle/ItaniumDemangle.cpp(946):
error #303: explicit type is missing ("int" assumed)
auto args = db.names.back().move_full();
^
detected during:
instant
How smart of me. I was confused because it looked like the version of curl
was the correct one. I'll run it again and see where it messes up this
time. Thanks for fixing that.
On Saturday, October 15, 2016 at 1:51:28 PM UTC-5, Erik Schnetter wrote:
>
> You didn't show the actual error message
You didn't show the actual error message. Debugging is easier if (after
seeing an error) you re-run with "make -j1", so that the error message
doesn't scroll away.
-erik
On Sat, Oct 15, 2016 at 1:41 PM, ABB wrote:
> I'm getting a new error. This is with the following make.user:
>
> LLVM_VER=svn
I'm getting a new error. This is with the following make.user:
LLVM_VER=svn
USEICC=1
USEIFC=1
USE_INTEL_MKL=1
USE_INTEL_MKL_FFT=1
USE_INTEL_LIBM=1
building directly on the (KNL) compute node (in parallel: make -j 68)
configure: amending tests/server/Makefile
configure: amending tests/libtest/M
Ok - thanks for the clarification. I will try to compile on the compute
node, not the login node.
I will submit a ticket to TACC and ask about cmake too. The version on the
compute node is 2.8.11.
On Friday, October 14, 2016 at 10:42:51 AM UTC-5, Erik Schnetter wrote:
>
> Julia runs some
Julia runs some of the code it generates as part of its bootstrapping
procedure. That is, traditional cross-compiling won't work. I think there's
a way around it, but it's not trivial. I would avoid this in the beginning.
-erik
On Fri, Oct 14, 2016 at 11:28 AM, ABB wrote:
> I was building on th
I was building on the (Haswell) front end. From some of the other issues I
looked at it appeared that I could specify the architecture even if I was
not actually building on that kind of system. But that could be totally
wrong, so I can try it on the KNL node if that's required.
When I put "
Were you building on a KNL node or on the frontend? What architecture did
you specify?
-erik
On Thu, Oct 13, 2016 at 9:38 PM, Valentin Churavy
wrote:
> Since KNL is just a new platform the default version of the LLVM compiler
> that Julia is based on does not support it properly.
> During our t
Since KNL is just a new platform the default version of the LLVM compiler
that Julia is based on does not support it properly.
During our testing at MIT we found that we needed to switch to the current
upstream of LLVM (or if anybody reads this at a later time LLVM 4.0)
You can do that by putting
Sigh... build failed. I'm including the last part that worked and the
error message which followed:
JULIA usr/lib/julia/inference.ji
essentials.jl
generator.jl
reflection.jl
options.jl
promotion.jl
tuple.jl
range.jl
expr.jl
error.jl
bool.jl
number.jl
int.jl
signal (4): Illegal instruction
w
Awesome. Thanks. I'll try it again then. I appreciate the help.
(Austin is also my name. I save space in my memory by going to school at,
living in and being a guy with the same name.)
On Thursday, October 13, 2016 at 1:40:09 PM UTC-5, Erik Schnetter wrote:
>
> AB
>
> You're speaking of Stam
AB
You're speaking of Stampede, if I might guess from the "austin" prefix in
your email address. I would treat the old and the new section of the
machines as separate, since they are not binary compatible. If you are
really interested in the KNL part, then I'd concentrate on these, and use
the dev
This is great - thanks for getting back to me so quickly.
To follow up, I have two small questions:
- To build specifically for the KNL system I should include something like
"JULIA_CPU_TARGET = knl" in the Make.user file?
- Part of the system is KNL, part of it is "Intel Xeon E5 Sandy Bridge a
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
shou
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
15 matches
Mail list logo