Package Details: scotch 7.0.7-2

Git Clone URL: https://aur.archlinux.org/scotch.git (read-only, click to copy)
Package Base: scotch
Description: Package for graph, mesh/hypergraph partitioning, static mapping, and sparse matrix block ordering
Upstream URL: https://gitlab.inria.fr/scotch/scotch
Licenses: CeCILL-C
Conflicts: ptscotch-openmpi, scotch_esmumps, scotch_esmumps5
Provides: ptscotch, ptscotch-openmpi, scotch_esmumps, scotch_ptesmumps
Submitter: None
Maintainer: ioquatix (MartinDiehl)
Last Packager: MartinDiehl
Votes: 41
Popularity: 0.028368
First Submitted: 2006-11-07 17:51 (UTC)
Last Updated: 2025-05-03 10:16 (UTC)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 Next › Last »

<deleted-account> commented on 2013-03-02 23:20 (UTC)

I ran into the issue described in the second paragraph of the 3) Compilation section of scotch_6.0.0_esmumps/INSTALL.txt Adding the following line to PKGBUILD worked for me, and should be fine as long as mpicc doesn't cross-compile: sed -i "/CCD/ c CCD\t\t= ${_prefix}/bin/mpicc" Makefile.inc

myles commented on 2013-02-15 15:02 (UTC)

Headers now install to /usr/include instead of /usr/include/scotch.

LWhitson2 commented on 2013-02-02 02:40 (UTC)

@CAVT Yes, I know of this problem but do not have an answer at this time. I am an OpenFOAM user myself and don't really know what to do. I would suggest you do a developmental install using the OF packaged scotch for the time being.

CAVT commented on 2013-02-02 01:48 (UTC)

@LWhitson: Thank you very much for your concern :). However, I'm facing an issue, and it's that both this package and the ptscotch-openmpi package try to install equally-called headers in the /usr/include/scotch folder. Have you faced that problem? Is there a workaround? Just to add, both packages compile perfectly, the problem appears when the final installation is to be made and pacman complaints.

jedbrown commented on 2013-02-01 17:20 (UTC)

... and even if this works, you should still ask upstream to make ptscotch capable of being built with a previously-installed scotch. Only by receiving many such requests are they likely to change. We would already use it from ptscotch-openmpi and ptscotch-mpich.

jedbrown commented on 2013-02-01 17:17 (UTC)

@LWhitson2 OpenFOAM does not have a problem depending on MPI, they just build ptscotch and it installs both libraries. We might be okay with static libraries here. If you want to try adding provides=(scotch) and check that (a) you don't pick up a transitive dependency on MPI and (b) the binary interface is compatible with stand-alone scotch, then I'll add it to this PKGBUILD. (I've been burned in similar ways by this package in the past and don't have time to test thoroughly.)

LWhitson2 commented on 2013-02-01 00:57 (UTC)

If you build scotch/ptscotch with OpenFOAM (currently version 5.11.1), it has two separate header files, scotch and ptscotch.

jedbrown commented on 2013-01-31 23:31 (UTC)

@LWhitson2 How does OpenFOAM do it in other environments? I'd be happy to accept patches, but I'm not interested in spending time on custom mediation of upstream's poorly-factored dependencies.

LWhitson2 commented on 2013-01-31 23:23 (UTC)

We have an interesting problem in that OpenFOAM requires both scotch and ptscotch yet there is no way to install both in this release. Thoughts.....

LWhitson2 commented on 2013-01-29 12:19 (UTC)

Sorry about that. I will take care of the package tonight.

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 Next › Last »