Sounds like a warning, is it serious? -- Performing Test MULTIPASS_TEST_2_petsc_works_allincludes -- Performing Test MULTIPASS_TEST_2_petsc_works_allincludes - Success -- PETSc requires extra include paths, but links correctly with only interface libraries. This is an unexpected configuration (but it seems to work fine).
Huaibao (Paul) Zhang *Gas Surface Interactions Lab* Department of Mechanical Engineering University of Kentucky, Lexington, KY, 40506-0503 *Office*: 216 Ralph G. Anderson Building *Web*:gsil.engineering.uky.edu On Mon, Dec 1, 2014 at 10:41 PM, paul zhang <[email protected]> wrote: > Problem solved! > This is a baby step for me. I actually have a code project which works > with petsc-3.1-p8, and configured with Cmake. As I attempted to update > PETSc, my old configuration flag never works. I have to start it over. > > Thanks a lot. > Paul > > > > On Mon, Dec 1, 2014 at 10:28 PM, Jed Brown <[email protected]> wrote: > >> paul zhang <[email protected]> writes: >> >> > Like this? still in trouble though... >> > >> > CMAKE_MINIMUM_REQUIRED(VERSION 2.8) >> > >> > set(PETSC_DIR /home/hzh225/LIB_CFD/nP/petsc-3.5.2) >> >> If you're going to manually set local paths in your build files, then >> CMake is definitely a waste of time. These are normally environment >> variables. >> >> > set(PETSC_ARCH /home/hzh225/LIB_CFD/nP/petsc-3.5.2/linux-gnu-intel) >> >> This is not how PETSC_ARCH works. It should probably be >> "linux-gnu-intel". Please read what PETSc's build prints or read the >> documentation. >> >> http://www.mcs.anl.gov/petsc/documentation/installation.html >> > >
