Dear Wolfgang, the case you describe:
Imagine you had two different versions of PETSc installed in /usr/ and > /usr/local/, and you had two different versions of Trilinos installed in > /usr/ and /usr/local/. If you want the version of PETSc in /usr and the > version of Trilinos from /usr/local/ to be used, what path do you want > to list first? > was not in my mind - since both are usually system pathes, where you typically need to have root-access. I thought on the case like PATH=/usr:/home/myuser/petsc (or the other way around). This case should be correctly detected by deal.II to pick up the user defined petsc lib and headers and not anything from the system pathes because of the order. I'm also not perfectly know, if it really is a deal.II-cmake detection problem (which I intended from the post of Timo) - or if it is "simple" wrong user environment (the former discussion in this thread). After the successful build of deal.II with candi, we state that the user have to either source all installed dependencies with the "enable.sh" bash script written by Timo or loading the runtime configuration with the (maybe out of the box imperfect) modulefile, before cmake / make / running a deal.II based application. This must be done at any time. Maybe that is the reason for the eclipse explanation of Daniel, which I do not really understand in the same way as Timo has answered (1st of the 3 above). Best Uwe -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
