Got it.  Thanks.
--Junchao Zhang

On Tue, Mar 12, 2019 at 2:01 PM Smith, Barry F. 
<bsm...@mcs.anl.gov<mailto:bsm...@mcs.anl.gov>> wrote:

  It is because you have  manual page documentation for it. The comment above 
it starts with /*@   if you don't want a manual page then remove the @ if you 
want a manual page but no stub then use /*@C

  Barry


> On Mar 12, 2019, at 1:46 PM, Zhang, Junchao via petsc-dev 
> <petsc-dev@mcs.anl.gov<mailto:petsc-dev@mcs.anl.gov>> wrote:
>
> I declared PETSC_INTERN PetscErrorCode VecLockWriteSet_Private(Vec,PetscBool) 
> in vecimp.h and defined it in src/vec/vec/interface/rvector.c.  I used 
> PETSC_INTERN and _Private since currently the function is only used in the 
> Vec packaged and is not public.  I met this compilation warning
> src/vec/vec/interface/ftn-auto/rvectorf.c:333:1: warning: implicit 
> declaration of function ‘VecLockWriteSet_Private’ 
> [-Wimplicit-function-declaration]
>  *__ierr = VecLockWriteSet_Private(
>  ^
> How to fix that? I do not think I need a Fortran stub for that. I found under 
> ftn-auto, not all .c functions have a Fotran counterpart. What is the rule?
> Thanks.
> --Junchao Zhang

Reply via email to