Closed sunpho84 closed 3 years ago
Never had this issue. Are you compiling with your modified build system?
In other words, this compile goes through fine for me:
CC=mpicc CXX=mpicxx F77=f77 \
CFLAGS="-mtune=znver2 -march=znver2 -O3 -mavx2 -mfma -fopenmp" \
LDFLAGS="-fopenmp" \
~/code/tmLQCD.quda_work/configure \
--enable-mpi \
--with-mpidimension=4 \
--enable-sse2 --enable-sse3 \
--with-cudadir=/usr/local/cuda/lib64 \
--with-qudadir=$(pwd)/../quda_develop/install_dir \
--with-limedir=$(pwd)/../lime/install_dir \
--with-lapack="-lblas -llapack"
using gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
, cuda_11.0_bu.TC445_37.28540450_0
and OpenMPI 4.0.3
No, I'm not using a modified build system, but I use gcc-10
$ gcc --version
gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0
I've checked that indeed, the error does not emerge using gcc-9. I don't know why gcc-9 is ignoring it and gcc-10 signals it
I'm guessing the compile and include orders differ slightly. This is clearly a bug which simply hasn't manifested.
When linking I get the following error
and so on. It looks like
block.h
contains a number of global variables, some of them are referred asextern
, some not, as it is the case forblk_gauge_eo
and the others. Theblock.h
header is included insideclovertm_operators.h
, which in turns is included in many place. This gives rise to the clash.Is this somehow new issue? I am in the quda_work branch, but it looks to me this is generic.