Re: [Starpu-devel] Configure option --with-magma not working

[Nathalie Furmento <nathalie.furmento@labri.fr>]

On 22/05/2014 22:49, Marc Sergent wrote:
> Le 22/05/2014 22:00, Nathalie Furmento a écrit :
> > On 22/05/2014 21:34, Marc Sergent wrote:
> > > Hi,
> > >
> > > It seems that the documented option --with-magma is not recognized 
> > > by the
> > > configure script. Actually, Magma can only be linked with StarPU by 
> > > setting
> > > a correct PKG_CONFIG_PATH to the magma.pc file path.
> > >
> > > Best regards,
> > >
> > > Marc
> >
> > Which version of StarPU?
>
> We're working with the latest StarPU release : 1.1.1.
>
> > Do you mean you need that option ? Or do you mean it should be 
> > removed from the documentation as it has been removed from 
> > configure.ac (to use instead pkg-config) ?
>
> Actually the only way to link StarPU with Magma is to define this kind 
> of PKG_CONFIG_PATH. I don't know what should
> be better, to let the configure detect Magma by itself of let the user 
> decide to link with Magma or not with the --with-magma
> option, like it's actually done for FxT for example.

There is 2 different things here: is it possible to enable or disable a 
library? and how is the location of the library defined?

> Actually, it seems that the make step fails if we only give a 
> PKG_CONFIG_PATH with this kind of error :
>
> Making all in src
> Making all in stencil
> make[3]: Entering directory 
> `/home/masliah/dev/starpu-1.1.1/examples/stencil'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory 
> `/home/masliah/dev/starpu-1.1.1/examples/stencil'
> make[3]: Entering directory `/home/masliah/dev/starpu-1.1.1/examples'
>   CC       cholesky_kernels.o
> cholesky/cholesky_kernels.c:22:19: fatal error: magma.h: No such file 
> or directory
>  #include "magma.h"

You should check in config.log if Magma has been properly detected and 
if the compilation of the example has the correct -I option.

> We tried to use the MAGMA_LIBS and MAGMA_CFLAGS environment variables 
> proposed by the ./configure --help, and we
> got another error :

These 2 variables are made available by configure itself, when using the 
command PKG_CHECK_MODULES to look for a module xxx, configure 
automatically gives you both options: set a correct pkg-config_PATH and 
defining xxx_libs and xxx_cflags.

> In file included from cholesky/cholesky_kernels.c:23:0:
> /home/masliah/dev/magma-1.3.0/include/magma_lapack.h:12:2: error: 
> #error Define one of ADD_, NOCHANGE, or UPCASE for how Fortran 
> functions are name mangled.
>  #error Define one of ADD_, NOCHANGE, or UPCASE for how Fortran 
> functions are name mangled.
>   ^
> In file included from 
> /home/masliah/dev/magma-1.3.0/include/magma_lapack.h:16:0,
>                  from cholesky/cholesky_kernels.c:23:
> /home/masliah/dev/magma-1.3.0/include/magma_zlapack.h:23:28: error: 
> ‘FORTRAN_NAME’ declared as function returning a function
>  #define blasf77_izamax     FORTRAN_NAME( izamax, IZAMAX )
>
>
> We found that it could be a missing -DADD_ compiling option.

Do you mean it is working by adding "-DADD_" to MAGMA_CFLAGS?

Cheers,

Nathalie