Package Details: petsc 3.21.0-2

Git Clone URL: https://aur.archlinux.org/petsc.git (read-only, click to copy)
Package Base: petsc
Description: Portable, extensible toolkit for scientific computation
Upstream URL: https://petsc.org
Keywords: computing scientific
Licenses: BSD
Provides: petsc4py
Submitter: heitzmann
Maintainer: MartinDiehl
Last Packager: MartinDiehl
Votes: 19
Popularity: 0.000098
First Submitted: 2018-02-24 11:36 (UTC)
Last Updated: 2024-04-03 06:01 (UTC)

Pinned Comments

MartinDiehl commented on 2022-10-06 10:26 (UTC)

@jrohwer

When building PETSc (more specifically, petsc4py), one test (ex100 from ksp) will fail if a previous (major) version is installed. I could not figure out why this happens. The solution would be to build in a clean root (which is a little bit complicated due to dependency on other AUR packages) or simply uninstall the old version before.

Any help to solve this issue is welcomed.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9

sigvald commented on 2018-06-22 15:20 (UTC)

This package should have

'hypre>=2.14: support for the hypre sparse system solver'

in optdepends. Note the version requirement.

sigvald commented on 2018-06-21 13:01 (UTC) (edited on 2018-06-21 17:10 (UTC) by sigvald)

Anyone familiar with this one?

/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2/src/mat/impls/hypre/mhypre.c: In function ‘hypre_array_destroy’:
/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2/src/mat/impls/hypre/mhypre.c:1453:37: error: macro "hypre_TFree" passed 2 arguments, but takes just 1
    hypre_TFree(ptr,HYPRE_MEMORY_HOST);
                                     ^
/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2/src/mat/impls/hypre/mhypre.c:1453:4: error: ‘hypre_TFree’ undeclared (first use in this function); did you mean ‘hypre_Free’?
    hypre_TFree(ptr,HYPRE_MEMORY_HOST);
    ^~~~~~~~~~~
    hypre_Free
/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2/src/mat/impls/hypre/mhypre.c:1453:4: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [gmakefile:150: arch-linux-c-opt/obj/mat/impls/hypre/mhypre.o] Error 1
make[2]: Leaving directory '/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2'
make[1]: *** [/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2/lib/petsc/conf/rules:81: gnumake] Error 2
make[1]: Leaving directory '/home/sigvald/Downloads/fenics/petsc/src/petsc-3.9.2'
**************************ERROR*************************************
  Error during compile, check arch-linux-c-opt/lib/petsc/conf/make.log
  Send it and arch-linux-c-opt/lib/petsc/conf/configure.log to petsc-maint@mcs.anl.gov
********************************************************************
make: *** [makefile:36: all] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

EDIT: Hypre needs to be v2.14.0, but the one on AUR is out-of-date (v2.11.0). Thanks to Satish Balay for pointing this out in a mail to me.

heitzmann commented on 2018-05-21 16:50 (UTC)

@mcovalt setting PETSC_ARCH messes up slepc... I don't have the time to figure out a fix right now, so I'll leave it as it is. Let me know if you can help with that.

mcovalt commented on 2018-05-15 18:46 (UTC)

Looks like my first comment didn't make it. Consider exporting PETSC_ARCH in addition to PETSC_DIR since many programs look for both environment variables to indicate a valid petsc installation is available.

mcovalt commented on 2018-05-15 18:45 (UTC)

Also, adding hypre and suitesparse to the list of optional dependencies could be considered since test_optdepends.sh looks for them.

linux_dream commented on 2018-05-09 18:51 (UTC)

Thank you @heitzmann. I've rebuilt scalapack, I think it was the culprit. I could upgrade petsc without any problem.

heitzmann commented on 2018-05-08 13:45 (UTC)

linux_dream, have you recompiled all your locally compiled dependencies after upgrading gcc-libs? That's probably the reason.

linux_dream commented on 2018-05-08 13:40 (UTC) (edited on 2018-05-08 13:41 (UTC) by linux_dream)

I can't seem to be able to upgrade 3.9.0-1 -> 3.9.1-1. I get:

UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):

Unable to find scalapack in default locations! Perhaps you can specify with --with-scalapack-dir=<directory> If you do not want scalapack, then give --with-scalapack=0 You might also consider using --download-scalapack instead</directory>

Any idea on how to fix the problem?

« First ‹ Previous 1 .. 4 5 6 7 8 9