On Tue, Sep 30, 2014 at 10:42 PM, Crooks, Cynthia J
<[email protected]> wrote:
> I am trying to build/install FEniCS on a SLES 11 SP 3 machine for one of our
> users. I am trying to use the opensuse12.1.platform as a template.
>
> So far I have done the following:
>
>
> Built/Installed python 2.7.7 with “—enable-shared”
> Installed subversion via the SLES distribution (zypper)
> Built/Installed SuiteSparse 4.3.1
> Built/Installed swig-2.0.12
> Built/installed boost-2_56_0
> Built/Installed openmpi-1.8.1
>
>
> Subversion was installed in the default location since it came from the SLES
> distribution. I did not installed the openmpi-devel or boost-devel from the
> SLES distribution because they required downgrades to openmpi.
>
> Python and openmpi were installed in their own directory trees in our
> globally accessible apps tree. SuiteSparse, swig and boost are all
> installed under the same top level directory as the FEinCS software.
>
> I ran “./dorsal.sh FEniCS/platforms/supported/opensuse12.1.platform”.
> Parmetis and trilinos seemed to install fine. Although
> trilinos-11.4.1-Source.tar.gz downloaded as a tar file (not gzipped); I
> renamed it to trilinos-11.4.1-Source.tar, gzip’d it, and updated the md5sum
> in the package file. Petsc downloaded, but the compile does not completed.
>
> The errors I am getting are :
>
> ====================
> Compiling Mumps; this may take several minutes
>
> ===============================================================================
>
> TESTING: check from
> config.libraries(/hpc/tstapps/src/FEniCS/1.4.0/petsc-3.4.2/config/BuildSystem/config/libraries.py:145)
> TESTING: checkInclude from
> config.headers(/hpc/tstapps/src/FEniCS/1.4.0/petsc-3.4.2/config/BuildSystem/config/headers.py:86)
> TESTING: checkSharedLibrary from
> PETSc.packages.MUMPS(/hpc/tstapps/src/FEniCS/1.4.0/petsc-3.4.2/config/BuildSystem/config/package.py:518)
> TESTING: configureLibrary from
> PETSc.packages.ml(/hpc/tstapps/src/FEniCS/1.4.0/petsc-3.4.2/config/BuildSystem/config/package.py:464)
> TESTING: check from
> config.libraries(/hpc/tstapps/src/FEniCS/1.4.0/petsc-3.4.2/config/BuildSystem/config/libraries.py:145)
> *******************************************************************************
> UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for
> details):
> -------------------------------------------------------------------------------
> --with-ml-lib=['/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libml.so'] and
> --with-ml-include=['/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/include/trilinos']
> did not work
> *******************************************************************************
>
> I have attached the configure.log.
The problem seems to be that Trilinos is not correctly linked against
the SuiteSparse libraries:
error message =
{/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_start'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_finish'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_free_factor'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `SuiteSparse_free'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_print_common'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `SuiteSparse_time'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_free_sparse'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_transpose'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `SuiteSparse_config'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `SuiteSparse_malloc'
/hpc/apps/SLES/3.0/x86_64/FEniCS/1.4.0/lib/libamesos.so.11: undefined
reference to `cholmod_analyze'
collect2: ld returned 1 exit status
}
Try setting UMFPACK_DIR in your platform file to point to the location
where you installed SuiteSparse (see also trilinos.package in Dorsal).
Then remove the dorsal_* files in the Trilinos source directory and
rebuild Trilinos. That should hopefully fix the problem.
Johannes
_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support
