Jose David Bermeol <[email protected]> writes:

> Hi, I've working with the new pardiso solver, I've testing in different 
> platforms and I found a problem. When I configure petsc I get the following 
> output:
>
> ...
> hypre:
>   Includes: -I/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/include
>   Library:  
> -Wl,-rpath,/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/lib 
> -L/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/lib -lHYPRE
>   Arch:
> mkl-pardiso:
>   Includes: -I/apps/rhel6/intel/composer_xe_2013.3.163/mkl/include
>   Library:  -Wl,--start-group 
> -L/apps/rhel6/intel/composer_xe_2013.3.163/mkl/lib/intel64 -lmkl_intel_lp64 
> -lmkl_intel_thread -lmkl_core -Wl,--end-group -lpthread -lm -liomp5
> MUMPS:
>   Includes: -I/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/include
>   Library:  
> -Wl,-rpath,/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/lib 
> -L/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/lib -lcmumps 
> -ldmumps -lsmumps -lzmumps -lmumps_common -lpord
> ...
>
> Everything look right to me. But when I'm compiling Petscwith cmake I get 
> that the includes are wrong
>
> [  0%] Building Fortran object 
> CMakeFiles/petsc.dir/src/sys/f90-mod/petscsysmod.F.o
> /apps/rhel6/intel/impi/4.1.0.030/bin64/mpiifort  -D__INSDIR__="" -fPIC -O3    
> -module include -I/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/include 
> -I/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/linux/include 
> -I/home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/-I/apps/rhel6/intel/composer_xe_2013.3.163/mkl/include
>  -I/apps/rhel6/valgrind/3.8.1/include 
> -I/apps/rhel6/intel/impi/4.1.0.030/intel64/include    -c 
> /home/jbermeol/Nemo5_Intel_E/libs/petsc/build-real/src/sys/f90-mod/petscsysmod.F
>  -o CMakeFiles/petsc.dir/src/sys/f90-mod/petscsysmod.F.o
>
> As you see there is a missing space, so I don't know to much about cmake or 
> how to fix this, so any help would be great.

Does your configure concatenate the strings without an intervening
space?  I don't think we've seen this before, but if you send a
reproducible test case, I'll look at it.

Attachment: pgpP0VJld76hf.pgp
Description: PGP signature

Reply via email to