Yes, this is due to a change in the API. But it is odd that this particular one is declared with a #define instead of typedef like the rest, so I have updated this type to use a typedef in the branch barry/fix-matsolvertype
Barry > On Jan 28, 2018, at 10:50 AM, Franck Houssen <[email protected]> wrote: > > Hello, > > In petscmat.h, the line "#define MatSolverPackage char*" shouldn't it be > replaced with "typedef char* MatSolverPackage" ? (like it's done for MatType > and others) > > When trying to use MatSolverPackage from a cpp file where "petsc.h" and > "petscmat.h" have been included I get this error : error: ‘MatSolverPackage’ > does not name a type; did you mean ‘MatSolverType’?. > Looks like this error does occur, or not, depending on compiler / OS : this > is OK with debian but not with ubuntu-trusty (line 2191 here > https://travis-ci.org/fghoussen/geneo4PETSc/jobs/334384582). > I would say the compile error can occur, or not, according to what > -fvisibility defaults to. > > Not sure of this... > > Franck
