Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Cannot find MPI

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Cannot find MPI


Chronologique Discussions 
  • From: Mathieu Faverge <mathieu.faverge@inria.fr>
  • To: Nathalie Furmento <nathalie.furmento@labri.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Cannot find MPI
  • Date: Mon, 16 Nov 2015 11:54:15 +0300
  • 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>

The -x test is definitely not the first one.

> grep mpicc configure
mpicc_path
with_mpicc
  --with-mpicc=<path to mpicc>
                          Path of the mpicc compiler
# Check whether --with-mpicc was given.
if test "${with_mpicc+set}" = set; then :
  withval=$with_mpicc;
            as_fn_error $? "--with-mpicc must be given a pathname" "$LINENO" 5
            mpicc_path=$withval
            DEFAULT_MPICC=smpicc
            DEFAULT_MPICC=mpicc
if ${ac_cv_path_mpicc_path+:} false; then :
  case $mpicc_path in
  ac_cv_path_mpicc_path="$mpicc_path" # Let the user override the test with a path.
    ac_cv_path_mpicc_path="$as_dir/$ac_word$ac_exec_ext"
  test -z "$ac_cv_path_mpicc_path" && ac_cv_path_mpicc_path="no"
mpicc_path=$ac_cv_path_mpicc_path
if test -n "$mpicc_path"; then
  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $mpicc_path" >&5
$as_echo "$mpicc_path" >&6; }
$as_echo "MPICC: $mpicc_path" >&1
if test ! -x $mpicc_path; then
    { $as_echo "$as_me:${as_lineno-$LINENO}: result: The mpicc compiler is not valid" >&5
$as_echo "The mpicc compiler is not valid" >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking mpicc path" >&5
$as_echo_n "checking mpicc path... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mpicc_path" >&5
$as_echo "$mpicc_path" >&6; }
MPICC=$mpicc_path
    cc_or_mpicc=$mpicc_path
        # For some reason, libtool uses gcc instead of mpicc when linking
        MPICC_LDFLAGS=`$mpicc_path --showme:link`
    cc_or_mpicc=$CC
CC_OR_MPICC=$cc_or_mpicc
as_dummy="$(dirname $mpicc_path):$PATH"


Le 16/11/2015 11:36, Nathalie Furmento a écrit :
56499581.9060509@labri.fr">
So, you should check the execute permission of the MPICC compiler. It's all the configure script does.

I attach a patch which gives a better error message.

Cheers,

Nathalie

On 16/11/2015 09:20, Mathieu Faverge wrote:
564991D1.1050107@inria.fr">
Hello,

whatever I do, mpicc or not, it is always the same result: MPI is disabled.

Mathieu

Le 16/11/2015 10:55, Nathalie Furmento a écrit :
Hi Mathieu,

configure only checks if the MPI compiler is executable.

if test ! -x $mpicc_path; then
	AC_MSG_RESULT(The mpicc compiler is not valid)

You should change the message below the if
to print the value of $mpicc_path.

Ah, i just saw you specified a value to --with-mpicc, you
should not need to do that. It looks like your system is
finding a MPI runtime in /sw/xc40/xalt/0.5.4/sles11.3_gnu4.9.2/bin/

Cheers,

Nathalie

On Nov 15, 11:26, Mathieu Faverge wrote:
> Hello,
> 
> Any ideas why I always get :
> 
>     StarPU Extensions:
>            MPI enabled:                                 no
> 
> I don't see why the test fails.
> 
> Mathieu


-- 
--
Mathieu Faverge
Maitre de conférence / Assistant Professor
Institut Polytechnique de Bordeaux - ENSEIRB-Matmeca
INRIA Bordeaux - Sud-Ouest, HiePACS Team
200 avenue de la vielle tour
33405 Talence Cedex
Phone: (+33) 5 24 57 40 73



-- 
--
Mathieu Faverge
Maitre de conférence / Assistant Professor
Institut Polytechnique de Bordeaux - ENSEIRB-Matmeca
INRIA Bordeaux - Sud-Ouest, HiePACS Team
200 avenue de la vielle tour
33405 Talence Cedex
Phone: (+33) 5 24 57 40 73



Archives gérées par MHonArc 2.6.19+.

Haut de le page