[petsc-dev] bfort broken with plex?

[Satish Balay]

Jed,

The sowing update is primarily required by
knepley/feature-plex-generic-distribute Hower I branched
'balay/update-sowing' off master - and merged to next.

Should I have directly commited to
knepley/feature-plex-generic-distribute?

Should I now merge balay/update-sowing into
knepley/feature-plex-generic-distribute?

There is one more fix required here: add MPI_Type_f2c() to mpiuni. And
this is dependent on knepley/feature-plex-generic-distribute +
balay/update-sowing

Trying to figure out where to commit this..

perhaps merge [or rebase] balay/update-sowing to
knepley/feature-plex-generic-distribute - and the commit directly to
knepley/feature-plex-generic-distribute?

thanks,
Satish

On Wed, 11 Sep 2013, Satish Balay wrote:

> looks like I forgot to push this earlier.
> 
> Its pushed to next now.
> 
> Satish
> 
> On Mon, 9 Sep 2013, Satish Balay wrote:
> 
> > updated sowing tarball - and pushed the updated sowing url to 'next'.
> > 
> > Satish
> > 
> > On Sun, 8 Sep 2013, Barry Smith wrote:
> > 
> > > 
> > >   Satish,
> > > 
> > > In next
> > > 
> > > /Applications/CMake 2.8-10.app/Contents/bin/cmake" -E cmake_link_script CMakeFiles/petsc.dir/link.txt --verbose=1
> > > Undefined symbols for architecture x86_64:
> > >   "_MPI_Datatype_f2c", referenced from:
> > >       _dmplexdistributedata_ in plexf.c.o
> > > ld: symbol(s) not found for architecture x86_64
> > > collect2: error: ld returned 1 exit status
> > > make[5]: *** [lib/libpetsc.dylib] Error 1
> > > make[4]: *** [CMakeFiles/petsc.dir/all] Error 2
> > > make[3]: *** [all] Error 2
> > > make[2]: *** [ccmake] Error 2
> > > make[1]: *** [cmake] Error 2
> > > 
> > > in bfort I find 
> > > 
> > > 	else if (strcmp( "MPI_Datatype", type ) == 0) {
> > > 	    sprintf( buf, "\n\tMPI_Datatype_f2c( *(%s) )", name );
> > > 
> > > but it seems it should be MPI_Type_f2c  (I guess the MPI folks don't care about consistency). 
> > > 
> > >   If I am correct about the mistake could you please fix the bfort repository version and crank up the release number?
> > > 
> > >    Thanks
> > > 
> > >      Barry
> > > 
> > > 
> > 
> > 
> 
>