>> petsc-dev with trunk libmesh
>
>
> Thanks. I'll see if I can get that build here.
>
> But I'm betting METIS is the tip of the iceberg - you listed a slew of
> packages on the configure command line that could potentially clash with our
> stuff.
>
> It may be possible to have libmesh use the
On Thu, Apr 26, 2012 at 2:36 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> >> petsc-dev with trunk libmesh
> >
> >
> > Thanks. I'll see if I can get that build here.
> >
> > But I'm betting METIS is the tip of the iceberg - you listed a slew of
> > packages on the configure
On Thu, 26 Apr 2012, Kirk, Benjamin (JSC-EG311) wrote:
> I've moved this to the -devel to set a bit for discussion. For things that
> we include as contributed packages, but we might reasonably expect other
> people to have, we might consider "prefixing" our includes in the old
> C-style? For
>> C-style? For background, David is having a parmetis version clash between
>> ours and the one included in petsc-dev with sieve enabled.
>
> This would work fine to avoid compile-time ambiguity, but there will
> still be multiple versions of the same functions floating around at
> link time, w
On Thu, 26 Apr 2012, Kirk, Benjamin (JSC-EG311) wrote:
>>> C-style? For background, David is having a parmetis version clash between
>>> ours and the one included in petsc-dev with sieve enabled.
>>
>> This would work fine to avoid compile-time ambiguity, but there will
>> still be multiple vers
On Thu, Apr 26, 2012 at 3:57 PM, Roy Stogner wrote:
>
> On Thu, 26 Apr 2012, Kirk, Benjamin (JSC-EG311) wrote:
>
> >>> C-style? For background, David is having a parmetis version clash
> between
> >>> ours and the one included in petsc-dev with sieve enabled.
> >>
> >> This would work fine to avo
>> So --with-parmetis=/foo
>>
>> and then in David's case he'd precompile parmetis and point petsc and
>> libmesh to the same one?
>
> Right - unless the default PETSc install already leaves parmetis
> headers and libraries someplace accessible, in which case only libMesh
> would need non-default
