Karl,

  I'll fix these

> On Nov 6, 2015, at 9:00 AM, PETSc checkBuilds <[email protected]> 
> wrote:
> 
> 
> 
> Dear PETSc developer,
> 
> This email contains listings of contributions attributed to you by
> `git blame` that caused compiler errors or warnings in PETSc automated
> testing.  Follow the links to see the full log files. Please attempt to fix
> the issues promptly or let us know at [email protected] if you are unable
> to resolve the issues.
> 
> Thanks,
>  The PETSc development team
> 
> ----
> 
> warnings attributed to commit 
> https://bitbucket.org/petsc/petsc/commits/1fc5b51
> ViennaCL: Fixed unused variable and function warnings.
> 
>  src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:107
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/11/06/build_next_arch-viennacl_frog.log]
>      
> /home/balay/petsc.clone-4/src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:107:62:
>  error: cannot convert 'PetscBool*' to 'const char*' for argument '3' to 
> 'PetscErrorCode PetscOptionsHasName(PetscOptions, const char*, const char*, 
> PetscBool*)'
> 
>  src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:115
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/11/06/build_next_arch-viennacl_frog.log]
>      
> /home/balay/petsc.clone-4/src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:115:62:
>  error: cannot convert 'PetscBool*' to 'const char*' for argument '3' to 
> 'PetscErrorCode PetscOptionsHasName(PetscOptions, const char*, const char*, 
> PetscBool*)'
> 
>  src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:123
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/11/06/build_next_arch-viennacl_frog.log]
>      
> /home/balay/petsc.clone-4/src/vec/vec/impls/seq/seqviennacl/vecviennacl.cxx:123:70:
>  error: cannot convert 'PetscBool*' to 'const char*' for argument '3' to 
> 'PetscErrorCode PetscOptionsHasName(PetscOptions, const char*, const char*, 
> PetscBool*)'
> 
> ----
> To opt-out from receiving these messages - send a request to 
> [email protected].

Reply via email to