forever compiling issue

[ThorinLee]

Hello everyone, I was running the compile.m file and matlab seems have stucked into the following output line. I wonder if anyone has met the same problem and does anyone have some ideas on this problem?

I was using matlab 2016a with cuda 8.0 and g++ 4.7.5 version.

vl_compilenn: MEX LINK: -outdir /home/myhome/twostreamfusion/matconvnet/matlab/mex -lmwblas -ljpeg -L/usr/local/cuda-8.0/lib64 -lcudart -lcublas -lmwgpu -L/usr/local/cuda-8.0/lib64 -lcudnn -largeArrayDims LDFLAGS=$LDFLAGS -Wl,-rpath -Wl,"/usr/local/cuda-8.0/lib64" LDFLAGS=$LDFLAGS -Wl,-rpath -Wl,"/usr/local/cuda-8.0/lib64" /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/vl_nnconv.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/data.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/datamex.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnconv.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnfullyconnected.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnsubsample.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnpooling.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnnormalize.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnbnorm.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/nnbias.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/im2row_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/subsample_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/copy_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/pooling_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/normalize_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/bnorm_cpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/tinythread.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/imread.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/im2row_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/subsample_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/copy_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/pooling_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/normalize_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/bnorm_gpu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/datacu.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/nnconv_cudnn.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/nnbias_cudnn.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/nnpooling_cudnn.o /home/myhome/twostreamfusion/matconvnet/matlab/mex/.build/bits/impl/imread_libjpeg.o

[ThorinLee]

well, I found this issue describes this problems and saying it is due to a bug in matlab r2016a, so I changed to matlab 2017a, and get out of the problem.