Hello.
> vyan2000@yan-home-530s ~/local/dealii/deal.II.7.1.0.petsc $ cat ~/.bashrc |
> grep PETSC_DIR
> export PETSC_DIR=/home/vyan2000/local/PPETSc/petsc-3.2-p5
> vyan2000@yan-home-530s ~/local/dealii/deal.II.7.1.0.petsc $ cat ~/.bashrc |
> grep PETSC_ARCH
> export PETSC_ARCH=O-deal-debug
That all looks good. Should that also be exported as your LD_LIBRARY_PATH
too? I think so. The link path needs to go straight to the PETSc lib
directory where the petsc library lives. That way ld can find it.
Adding this to the end of your ~/.bashrc (and then source ~/.bashrc)
export LD_LIBRARY_PATH=$PETSC_DIR/$PETSC_ARCH/lib:${LD_LIBRARY_PATH}:
should do the trick.
You can check it in your shell by
echo $PETSC_DIR <- should return PETSc directory
echo $PETSC_ARCH <- should return PETSc architecture
echo $LD_LIBRARY_PATH <- should return the complete path to PETSc's lib
directory.
> Also, I checked the config.log again and those variables are read in
> successfully by Deal.II. But I am not sure what the PETSC_MPIUNI_LIB is.
Yes, if deal.II goes through the configure process there should be no
problem with your PETSc setup; your config.log looks sane. It's just
getting the linking done right in the environment (as above).
PETSC_MPIUNI_LIB is archaic and is not a relevant flag for petsc-3.x -
it's all built into one big PETSc library now.
How does that work out for you?
Best,
Toby
-----
Toby D. Young
Assistant Professor
Institute of Fundamental Technological Problems
Polish Academy of Sciences
ul Adolfa Pawinskiego 5b
02-106 Warsaw
Poland
www: http://www.ippt.gov.pl/~tyoung
skype: stenografia
_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
