Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

2021-04-07 Thread Matthew Knepley
On Wed, Apr 7, 2021 at 5:47 PM Scott Kruger wrote: > On 2021-04-06 14:44, Matthew Knepley did write: > > > > Does spack have some magic for this we could use? > > > > > > > > > > spack developed the archspec repo to abstract all of these issues: > > > https://github.com/archspec/archspec > > > >

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

2021-04-07 Thread Scott Kruger
On 2021-04-06 14:44, Matthew Knepley did write: > > > Does spack have some magic for this we could use? > > > > > > > spack developed the archspec repo to abstract all of these issues: > > https://github.com/archspec/archspec > > > I do not love it. Besides the actual code (you can always

Re: [petsc-dev] (arm64) could not find object file symbol for symbol ___muldc3

2021-04-07 Thread Barry Smith
Ok, thanks. I am not sure how to handle it. libgcc_s.1.dylib never appears in the configure process and we don't actually test that the Fortran compiler can link C; for 25 years it just always could. Barry > On Apr 7, 2021, at 10:49 AM, Blaise A Bourdin wrote: > > No luck with -lgcc

Re: [petsc-dev] ?????? Petsc: Error code 1

2021-04-07 Thread Satish Balay via petsc-dev
There are always diffs (between different compilers, versions, hardware) - doesn't necessarily mean failures. Very large diffs [as Barry mentioned] might require a closer look. Depending upon your purpose - you might consider that you have a valid petsc install and start using it. Obviously -

Re: [petsc-dev] DMNetwork static sizing

2021-04-07 Thread Matthew Knepley
On Tue, Apr 6, 2021 at 7:44 PM Abhyankar, Shrirang G < shrirang.abhyan...@pnnl.gov> wrote: > Hong, > > It was just to keep things simple. We can have an API (and a run-time > option) for setting the max. number of components instead of a configure > option. I can work on making this change. >