Re: [julia-users] complex int ? A gcc-ism?
Issue submitted. https://github.com/JuliaLang/julia/issues/17145 V.
[julia-users] complex int ? A gcc-ism?
My attempt to install Julia with the Intel compilers flounders on make[2]: Entering directory `/work/00434/eijkhout/julia/julia-master/src' CC usr/lib/libccalltest.so /work/00434/eijkhout/julia/julia-master/src/ccalltest.c(295): error: _Complex can only be used with float, double, or long double types complex int r1; ^ /work/00434/eijkhout/julia/julia-master/src/ccalltest.c(296): error: _Complex can only be used with float, double, or long double types complex int r2; ^ >From all the googling that I've done, "complex int" is not legal C, but seems a gcc extension. True? This looks like a test file, and the only place it ever occurs. Shall I just edit it out and call my installation completely? Victor.
[julia-users] Re: Installing with Intel compiler
I wish I could supply some general help. Here's the story as I understand it: the latest Intel compilers rely on gcc for full C++11 and higher support. That means you have to specify some tricky combination of Intel & gcc setup. On my system this was done by someone else, so I don't know the details. Here's the script that loads C++ support: prepend_path("PATH","/opt/apps/gcc/4.9.1/bin") prepend_path("LD_LIBRARY_PATH","/opt/apps/gcc/4.9.1/lib") prepend_path("LD_LIBRARY_PATH","/opt/apps/gcc/4.9.1/lib64") (that's lua, btw, but the meaning is obvious) If you know what to ask me I'll be happy to dig further, but right now I can't explicitly tell you what Intel icpc uses from gcc to obtain C++1y functionality. Victor.
[julia-users] Re: Installing with Intel compiler
Ok, feel free to close this ticket. By putting enough gcc stuff in the path I managed to get it to install in the Intel compiler. At least I think it's doing that. The configure messages are still quite ambiguous. V.
[julia-users] Installing with Intel compiler
I'm trying to install in the the Intel15 compiler on Linux. In the Make.inc I've set ever ICC to true that I ccould find. The output is a complete mix of gcc and icc. Any suggestions for how to disabuse it of the notion that it's using gcc? checking whether we are using the GNU C compiler... yes checking whether icc accepts -g... yes checking for icc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether icpc accepts -g... yes checking how to run the C preprocessor... icc -E checking whether GCC or Clang is our host compiler... gcc checking build system type... x86_64-redhat-linux-gnu checking host system type... x86_64-redhat-linux-gnu checking target system type... x86_64-redhat-linux-gnu checking type of operating system we're going to host on... Linux checking type of operating system we're going to target... Linux checking target architecture... x86_64 checking whether GCC is new enough... no configure: error: The selected GCC C++ compiler is not new enough to build LLVM. Please upgrade to GCC 4.7. You may pass --disable-compiler-version-checks to configure to bypass these sanity checks.