AUR (en) - petsc-git

Search Criteria

Package Details: petsc-git 3.21.1.r89.g70699e4d17e-1

Git Clone URL:	https://aur.archlinux.org/petsc-git.git (read-only, click to copy)
Package Base:	petsc-git
Description:	Portable, extensible toolkit for scientific computation
Upstream URL:	https://petsc.org
Licenses:	BSD-2-Clause
Conflicts:	petsc
Provides:	petsc, petsc4py
Submitter:	heitzmann
Maintainer:	carlosal1015
Last Packager:	carlosal1015
Votes:	2
Popularity:	0.000000
First Submitted:	2019-02-05 14:41 (UTC)
Last Updated:	2024-05-29 14:47 (UTC)

Git Clone URL:

https://aur.archlinux.org/petsc-git.git (read-only, click to copy)

Package Base:

petsc-git

Description:

Portable, extensible toolkit for scientific computation

Upstream URL:

https://petsc.org

Licenses:

BSD-2-Clause

Conflicts:

petsc

Provides:

petsc, petsc4py

Submitter:

heitzmann

Maintainer:

carlosal1015

Last Packager:

carlosal1015

Votes:

Popularity:

0.000000

First Submitted:

2019-02-05 14:41 (UTC)

Last Updated:

2024-05-29 14:47 (UTC)

Latest Comments

1 2 3 Next › Last »

entshuld commented on 2024-05-07 09:12 (UTC)

Would you consider disowning this package?

MarsSeed commented on 2023-11-06 13:08 (UTC)

Hi,

Please kindly make this build from the 'main' branch, and create a separate package, petsc-release-git for the stable maintenance branch.

By default, a -git package should build the active development branch. For any other branch, a branch-specific naming is needed, and this is the best practice to avoid confusion.

Thank you in advance.

carlosal1015 commented on 2022-11-01 16:49 (UTC)

Yeap, today I will push up to date package.

entshuld commented on 2022-11-01 12:44 (UTC)

Any chance that this package actually builds from the current git main branch? 3.16.3 is from January (10 months ago).

entshuld commented on 2022-10-02 17:13 (UTC)

@carlosal1015 you are very right, but if you don't do that, you'll eventually have different issues (which I don't remember at this moment). Is this what you mean with "modernize"? You could try with a pacman command to get the current version of your HYPRE, but I am sure there was a good reason for which I replaced "hypre" with "hypre=...". In any case, let's see who has issues with the new version. I don't have access to my system right now, but I'll do it later.

carlosal1015 commented on 2022-07-06 16:10 (UTC)

Hi, I have the following message error:

 -> Could not find all required packages:
    hypre=2.23.0 (Wanted by: petsc-git)

I think that is not a good idea pin the version hypre=2.23.0.

urbainvaes commented on 2021-02-04 10:08 (UTC)

I think chrpath should be added in make-depends?

heitzmann commented on 2020-05-21 12:17 (UTC)

Indeed I just copied a version that seemed to be working because I didn't have the time to fully check it. I've gone through the external packages now and left all that were working as external downloads. Party and Suitesparse are notable exceptions for now.

This last PKGBUILD update seems to be working properly now. Let me know if I missed anything.

killozap commented on 2020-05-21 01:38 (UTC)

heitzmann: I checked, the previous PKGBUILD does indeed not compile with latest gcc. But at the beginning of the new script test_optdepends.sh, the for loop for the desired external packages can be uncommented. Seems to work as before, with the latest gcc.

Btw, in PKGBUILD on l.103 there is a $ missing: --CXXOPTFLAGS="CXXOPTFLAGS" Thanks

heitzmann commented on 2020-05-20 19:27 (UTC)

Hi killozap, I haven't been using this package for a while. I got a message that it was not working anymore due to the latest gcc update, so I updated to this working version. Have you tried installing the previous PKGBUILD version with the latest gcc?