wrong compiler used during instant build

Issue #1 resolved
Former user created an issue

cat instant_module_672321a1b160ae64201af8d497e52b999174cb1a/compile.log:

running build_ext building '_instant_module_672321a1b160ae64201af8d497e52b999174cb1a' extension creating build creating build/temp.linux-x86_64-2.7 /scinet/gpc/mpi/openmpi/1.6.4-gcc-v4.7.2/bin/mpicc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/s/steinman/dolores/Build/include -I/home/s/steinman/dolores/Build/include -I/home/s/steinman/dolores/Build/include/python2.7 -c instant_module_672321a1b160ae64201af8d497e52b999174cb1a_wrap.cxx -o build/temp.linux-x86_64-2.7/instant_module_672321a1b160ae64201af8d497e52b999174cb1a_wrap.o -O0 cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC but not for C++ [enabled by default] creating build/lib.linux-x86_64-2.7

/scinet/gpc/mpi/openmpi/1.6.4-gcc-v4.7.2/bin/mpicxx -pthread -shared build/temp.linux-x86_64-2.7/instant_module_672321a1b160ae64201af8d497e52b999174cb1a_wrap.o -L/home/s/steinman/dolores/Build/lib -L/home/s/steinman/dolores/Build/lib -lboost_math_tr1 -lpython2.7 -o build/lib.linux-x86_64-2.7/_instant_module_672321a1b160ae64201af8d497e52b999174cb1a.so

g++: error: build/temp.linux-x86_64-2.7/instant_module_672321a1b160ae64201af8d497e52b999174cb1a_wrap.o: No such file or directory error: command '/scinet/gpc/mpi/openmpi/1.6.4-gcc-v4.7.2/bin/mpicxx' failed with exit status 1

note that in the first compilation it's using mpicc instead of mpicxx. Setting both CC and CXX to mpicxx allows it to continue, but it shouln't be using the $CC variable in the first line.

when using gcc/g++ this works without any changes.

Comments (4)

  1. Johan Hake

    What version of instant does this issue relate to? We have recently updated the whole JIT chain in FEniCS to use CMake to address this particular issue.

    It looks like your error report relate to an older instant using distutils. Have you tried upgrade to master for all packages?

    Johan

  2. Jack Hale

    I have a similar issue on mac. Even though I have compiled with gcc-4.7 I get the clang compilers selected by default when using instant\cmake. A fix is to set both CC and CXX, but I have to do this manually every time I open a terminal so as not to mess with other aspects of my system.

  3. Johan Hake

    Is it the same error message in the log file? If so that indicates that you are not using CMake. Could you please post the content of the log file when you compile with cmake?

  4. Log in to comment