[Octopus-users] compiling octopus_mpi 3.1.0 with mpich in anon-standard directory
daniel.joubert at physics.org
Thu Jun 11 15:41:14 WEST 2009
Thank you for your response.
I managed to sort out the configure and compilation problems.
For information, the pathscale c compiler, pathcc version 2.9.99, does not seem able to compile the all the routines in /src/beak. The error message is included below. I compiled with the gcc compiler which seems to work on this IBM e1350 Cluster.
pathcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I../../external_libs/spglib/src -I../../liboct_parser -I../../external_libs/metis-4.0/ -I../../external_libs/zoltan/include -g -O2 -I/CHPC/usr/local/gsl-1.9/include -MT operate_ri_vec.o -MD -MP -MF .deps/operate_ri_vec.Tpo -c -o operate_ri_vec.o operate_ri_vec.c
operate_ri_vec.c: In function `zoperate_ri_vec__':
operate_ri_vec.c:264: warning: passing arg 1 of `_mm_storeu_pd' from incompatible pointer type
operate_ri_vec.c:287: warning: passing arg 1 of `_mm_loadu_pd' from incompatible pointer type
operate_ri_vec.c:289: warning: passing arg 1 of `_mm_storeu_pd' from incompatible pointer type
### Assertion failure at line 6208 of ../../be/cg/x8664/expand.cxx:
### Compiler Error in file operate_ri_vec.c during Code_Expansion phase:
### Exp_Intrinsic_Op: unsupported intrinsic ((null))
pathcc INTERNAL ERROR: /opt/pathscale/lib/2.9.99/be returned non-zero status 1
Please report this problem to <support at pathscale.com>.
Problem report saved as /CHPC/home/djoubert/.ekopath-bugs/pathcc_error_LVNizS.i
Please review the above file and, if possible, attach it to your problem report.
make: *** [operate_ri_vec.o] Error 1
From: Xavier Andrade xavier at tddft.org
Date: Thu, 11 Jun 2009 08:17:37 +0100
To: "Daniel.joubert" daniel.joubert at physics.org
Subject: Re: [Octopus-users] compiling octopus_mpi 3.1.0 with mpich in anon-standard directory
> Hi Daniel,
> On Thu, 11 Jun 2009, Daniel.joubert wrote:
> > Installation of octopus_mpi on a system with mpich in standard
> > directories in /usr/local/ works fine. I am now trying to compile
> > octopus_mpi 3.1.0 on an IBM e1350 Cluster with the mpich installation in
> > a 'non-standard' directory. Specifying --enable-mpi="root directory of
> > mpich2 installation" does not work. It seems that the mpich libraries
> > are not found during configuration. . What information has to supplied
> > to configure when the mpich is installed in non-standard directories?
> Besides library information, you also have to pass the flags for the
> compiler to find MPI headers/modules both for C and Fortran, perhaps this
> is what causing problems. You can check why the compilation failed in the
> config.log file.
> In any case, with mpich is better to specify as compilers the wrapper
> scripts (mpicc and mpif90) instead of passing the flags directly.
More information about the Octopus-users