Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Build error with icc (trunk)

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Build error with icc (trunk)


Chronologique Discussions 
  • From: Keisuke Fukuda <fukuda@matsulab.is.titech.ac.jp>
  • To: Cyril Roelandt <cyril.roelandt@inria.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Build error with icc (trunk)
  • Date: Wed, 12 Dec 2012 08:56:44 +0900
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

Nathalie and Cyril,

Thanks for the replies

Although Cyril already clearly described the problem, I uploaded make log
and config.log file.
https://gist.github.com/4263344
(Go down to see the make log because config.log is very long)

In addition, I carefully checked 1.0 branch and 1.0.4 tarball again,  
and I found that gcc is implicitly used (that might be another problem in a strict 
performance evaluation).

Regards,
Keisuke



On Wed, Dec 12, 2012 at 3:00 AM, Cyril Roelandt <cyril.roelandt@inria.fr> wrote:
On 12/11/2012 10:01 AM, Keisuke Fukuda wrote:
Dear StarPU developers,

On the trunk (rev 8284), there's a build problem on TSUBAME, which has icc
as its default C compiler.

Whole the build log is attached, but the part looks like the following.

icc: command line warning #10006: ignoring unknown option '-dumpspecs'
icc: command line error: no files specified; for help type "icc -help"

The "-dumpspecs" option is GCC-specific, so ICC fails.

The command line that fails is:

/opt/cuda/4.1//bin/nvcc ring_kernel.cu -c -o ring_kernel.o -ccbin /usr/apps/openmpi/1.4.2/intel/bin/mpicc -I/opt/cuda/4.1/include/ -m64 --compiler-options -fno-strict-aliasing  -I../../include/ -I../../include/ -I/home/usr1/11M37264/local/include -I/usr/include/libxml2

The "-ccbin" option specifies the compiler used by nvcc. Here, it is ".../intel/bin/mpicc", which is probably a wrapper around icc. I think that nvcc should be able to find GCC if it is installed - is gcc installed on your machine ?

I don't know if there is a way to remove the "-dumpspecs" option from the commande line.



1.0-branch and 1.0.4 tar ball have no problem.

That is quite surprising.


Regards,
Cyril Roelandt.



--
------------------------------------------
FUKUDA, Keisuke<fukuda@matsulab.is.titech.ac.jp>
Dept. of Math. & Comp. Sciences
Satoshi Matsuoka Lab.,
Tokyo Institute of Technology

福田圭祐 <fukuda@matsulab.is.titech.ac.jp>
東京工業大学 数理・計算科学専攻 松岡研究室





Archives gérées par MHonArc 2.6.19+.

Haut de le page