I am building a fresh PETSc with GNU on Titan and I get these warnings
about incompatible pointers in calls in PlexPartition to MarMetis.
Mark
/lustre/atlas1/geo127/proj-shared/petsc/src/dm/impls/plex/plexpartition.c:
In function 'PetscPartitionerPartition_ParMetis':
/lustre/atlas1/geo127/proj-sh
On Mon, Oct 29, 2018 at 4:56 PM Mark Adams via petsc-dev <
petsc-dev@mcs.anl.gov> wrote:
> I am building a fresh PETSc with GNU on Titan and I get these warnings
> about incompatible pointers in calls in PlexPartition to MarMetis.
>
Looks like PETSc has 64-bit ints and ParMetis has 32-bit ints. J
On Mon, Oct 29, 2018 at 5:01 PM Matthew Knepley wrote:
> On Mon, Oct 29, 2018 at 4:56 PM Mark Adams via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> I am building a fresh PETSc with GNU on Titan and I get these warnings
>> about incompatible pointers in calls in PlexPartition to MarMetis.
>>
both 'long' and 'long long' should be 64bit.
Did this work before - and change today? [i.e due to one of the PR merges?]
Satish
On Mon, 29 Oct 2018, Matthew Knepley via petsc-dev wrote:
> On Mon, Oct 29, 2018 at 4:56 PM Mark Adams via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
> > I am buil
Can you send corresponding logs?
Satish
On Mon, 29 Oct 2018, Mark Adams via petsc-dev wrote:
> I am building a fresh PETSc with GNU on Titan and I get these warnings
> about incompatible pointers in calls in PlexPartition to MarMetis.
>
> Mark
>
> /lustre/atlas1/geo127/proj-shared/petsc/src/dm
On Mon, Oct 29, 2018 at 5:19 PM Balay, Satish wrote:
> both 'long' and 'long long' should be 64bit.
>
> Did this work before - and change today? [i.e due to one of the PR merges?]
>
I am not sure, but probably not. I don't always check the makelogs and I am
just getting this machine/compiler wor
On Mon, 29 Oct 2018, Mark Adams via petsc-dev wrote:
> On Mon, Oct 29, 2018 at 5:19 PM Balay, Satish wrote:
>
> > both 'long' and 'long long' should be 64bit.
> >
> > Did this work before - and change today? [i.e due to one of the PR merges?]
> >
>
> I am not sure, but probably not. I don't alw
On Mon, 29 Oct 2018, Mark Adams via petsc-dev wrote:
> On Mon, Oct 29, 2018 at 5:26 PM Balay, Satish wrote:
>
> > Can you send corresponding logs?
>
Source:
#include "confdefs.h"
#include "conffix.h"
#ifdef PETSC_HAVE_STDLIB_H
#include
#endif
#include
int main() {
MPI_Aint size;
int i
>
>
> Pushing language C
> Popping language C
> Executing: cc -o /tmp/petsc-yiGfSd/config.packages.MPI/conftest -O
> /tmp/petsc-yiGfSd/config.packages.MPI/conftest.o -ldl
> Testing executable /tmp/petsc-yiGfSd/config.packages.MPI/conftes
On Mon, 29 Oct 2018, Mark Adams via petsc-dev wrote:
> >
> >
> > Pushing language C
> > Popping language C
> > Executing: cc -o /tmp/petsc-yiGfSd/config.packages.MPI/conftest -O
> > /tmp/petsc-yiGfSd/config.packages.MPI/conftest.o -ldl
I was able to run ksp ex56 manually. This machine requires an inscrutable
workflow. I built the code in my home directory, copied the executable to a
working directory and ran there. I have seen my colleagues do this copy
business that is clearly not in PETSc tests. I don't understand it but I
can
11 matches
Mail list logo