[petsc-dev] public functions with no manual pages

2018-08-22 Thread Smith, Barry F.
DMSNESCheckFromOptions() DMTSCheckFromOptions()

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Satish Balay
On Wed, 22 Aug 2018, Jed Brown wrote: > Matthew Knepley writes: > > > Someone changes an interface, and you pull the change. The header changes > > will cause all the C files > > using that API to rebuild. However, the doc system (sowing) runs bfort on > > the C file to generate the Fortran > >

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Jed Brown
"Jose E. Roman" writes: > Another fix is to have a custom Fortran stub for KSPFGMRESModifyPCKSP() and > KSPFGMRESModifyPCNoChange(), rather than an automatic Fortran stub. That is, > change /*@ to /*@C and add a definition for these functions in zmodpcff.c Absolutely disgusting.

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Jed Brown
Matthew Knepley writes: > Someone changes an interface, and you pull the change. The header changes > will cause all the C files > using that API to rebuild. However, the doc system (sowing) runs bfort on > the C file to generate the Fortran > binding. It runs on all headers at once, so there is

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Patrick Sanan
Thanks all! "make allfortranstubs && make" is certainly practical enough for me. I'd naively been assuming that "make deletefortranstubs && make" would have the same effect. 2018-08-22 13:09 GMT+02:00 Jose E. Roman : > > > > El 22 ago 2018, a las 12:52, Matthew Knepley > escribió: > > > > On

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Jose E. Roman
> El 22 ago 2018, a las 12:52, Matthew Knepley escribió: > > On Wed, Aug 22, 2018 at 6:35 AM Lawrence Mitchell wrote: > > > On 22 Aug 2018, at 10:04, Patrick Sanan wrote: > > > > This happens fairly frequently when I try to switch/update branches of > > PETSc (here invoked by building my

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Matthew Knepley
On Wed, Aug 22, 2018 at 6:35 AM Lawrence Mitchell wrote: > > > On 22 Aug 2018, at 10:04, Patrick Sanan wrote: > > > > This happens fairly frequently when I try to switch/update branches of > PETSc (here invoked by building my own code, but the error message looks > the same with "make check"):

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Lawrence Mitchell
> On 22 Aug 2018, at 10:04, Patrick Sanan wrote: > > This happens fairly frequently when I try to switch/update branches of PETSc > (here invoked by building my own code, but the error message looks the same > with "make check"): > > $ make >

[petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

2018-08-22 Thread Patrick Sanan
This happens fairly frequently when I try to switch/update branches of PETSc (here invoked by building my own code, but the error message looks the same with "make check"): $ make /Users/patrick/petsc-stagbl/arch-darwin-stagbl-double-extra-debug/bin/mpicc -o runme.o -c -Wall -Wwrite-strings