I made a fresh start after setting PETSC_DIR and PETSC_ARCH (would be good to 
warn the user to do this in advance!) and after several hours got to the 
following point:

./dorsal.sh
...

TESTING: configureLibrary from 
PETSc.packages.hypre(/home/lichtner/FEniCS/stable/src/petsc-3.4.2/config/BuildSystem/config/package.py:464)
            
**************************************************************************************************
            Please register to use hypre at 
https://computation.llnl.gov/casc/linear_solvers/sls_hypre.html
            
**************************************************************************************************

where the build process appears to hang. Does this mean I have to register to 
use hypre (I don't see anywhere to do this on the hypre web page) which I don't 
think I really need anyway? Maybe this is a PETSc issue?

Thanks, ...Peter

On Dec 20, 2013, at 3:42 PM, Peter Lichtner <[email protected]> wrote:

> Greetings: I set the parmetis project to download parmetis-4.0.3 and that 
> seemed to work. However, installing fenics using dorsal failed later on after 
> setting PETSC_DIR and rerunning:
> 
> ./dorsal.sh
> ...
> 
> Install the project...
> -- Install configuration: "RELEASE"
> -- Installing: /usr/local/include/Trilinos_version.h
> CMake Error at cmake_install.cmake:36 (FILE):
>   file INSTALL cannot copy file
>   
> "/home/lichtner/FEniCS/stable/src/trilinos-11.4.1-Source/dorsal_build_dir/././Trilinos_version.h"
>   to "/usr/local/include/Trilinos_version.h".
> 
> 
> make: *** [install] Error 1
> make: Leaving directory 
> `/home/lichtner/FEniCS/stable/src/trilinos-11.4.1-Source/dorsal_build_dir'
> Failure with exit status: 2
> Exit message: There was a problem building trilinos-11.4.1-Source.
> 
> My dorsal config file looks like:
> 
> dorsal.cfg
> # Global configuration variables go here. You will want to tweak this
> # file to suit your needs. If you want to keep local changes that are
> # not overwritten by repository updates, those can be written
> # to local.cfg instead (entries there will override those in this file).
> 
> # Meta-project to build
> PROJECT=FEniCS
> # Where do you want the downloaded source files to go?
> # DOWNLOAD_PATH=${HOME}/Work/${PROJECT}/src
> DOWNLOAD_PATH=/home/lichtner/FEniCS/stable/src
> # Where do you want the compiled software installed?
> # INSTALL_PATH=${HOME}/Work/${PROJECT}
> INSTALL_PATH=/home/lichtner/FEniCS/stable/fenics
> # How many processes would you like to build using?
> PROCS=1
> # Would you like to build stable versions of FEniCS projects?
> STABLE_BUILD=true
> # Would you like to use snapshots when using STABLE_BUILD=false?
> USE_SNAPSHOTS=false
> 
> So not sure I understand why installing in /usr/local/...
> 
> Thanks for any help, ...Peter
> 
>> Greeting: I am trying to install FEniCS on Ubuntu 12.04 using the automated 
>> dorsal installation. However, I get an error trying to download parmetis:
>> 
>> ./dorsal.sh
>> ...
>> -- Installing: /home/lichtner/FEniCS/stable/fenics/lib/libCGAL.so
>> make: Leaving directory 
>> `/home/lichtner/FEniCS/stable/src/CGAL-4.1/dorsal_build_dir'
>> Fetching parmetis-4.0.2
>> --2013-12-20 12:19:28--  
>> http://glaros.dtc.umn.edu/gkhome/fetch/sw/parmetis/parmetis-4.0.2.tar.gz
>> Resolving glaros.dtc.umn.edu (glaros.dtc.umn.edu)... failed: Name or service 
>> not known.
>> wget: unable to resolve host address `glaros.dtc.umn.edu'
>> Unpacking parmetis-4.0.2
>> parmetis-4.0.2.tar.gz does not exist. Please download first.
>> 
>> Looks like there is a newer release parmetis-4.0.3 which may be why it is 
>> not found. Can this newer release be used?
>> 
>> Second: Not clear to me where to put parmetis-4.0.x.tar.gz when downloaded.
>> 
>> Thanks for any help,
>> ...Peter
> 
> ________________
> Peter Lichtner
> Santa Fe, NM 87507
> (505) 692-4029 (c)
> OFM Research
> 

________________
Peter Lichtner
Santa Fe, NM 87507
(505) 692-4029 (c)
OFM Research

_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to