> El 11 mar 2016, a las 17:28, Satish Balay <ba...@mcs.anl.gov> escribió: > > There is one more broken build due to cuda changes. > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/make_next_arch-linux-pkgs-dbg-ftn-interfaces_crank.log > >>>>>>>> > /sandbox/petsc/petsc.clone-3/include/petsc/finclude/ftn-auto/petscvec.h90:740.52: > Included at > /sandbox/petsc/petsc.clone-3/include/petsc/finclude/petscvec.h90:9: > Included at /sandbox/petsc/petsc.clone-3/src/vec/f90-mod/petscvecmod.F:25: > > subroutine VecScatterInitializeForGPU(a,b,c,z) > 1 > Error: Symbol 'vecscatterinitializeforgpu' at (1) already has an explicit > interface > <<<< > > I see there are 2 impls of this function each in - resulting in 2 > 'intercace' definitions generated - causing this error. > > src/vec/vec/utils/veccusp/vscatcusp.c > src/vec/vec/utils/veccuda/vscatcuda.c > > Perhaps they shoud be merged into a single one? > > Satish
Yes, we will merge them in src/vec/vec/utils/vscat.c Jose