conda-forge / scotch-feedstock

A conda-smithy repository for scotch.

About scotch-pkgs-feedstock

Feedstock license: BSD-3-Clause

About scotch-pkgs

Home: https://www.labri.fr/perso/pelegrin/scotch/

Package license: CECILL-C

Summary: SCOTCH: Static Mapping, Graph, Mesh and Hypergraph Partitioning, and Parallel and Sequential Sparse Matrix Ordering Package

Development: https://gitlab.inria.fr/scotch/scotch

Documentation: http://gforge.inria.fr/docman/?group_id=248&dirid=326

Software package and libraries for sequential and parallel graph partitioning, static mapping and clustering, sequential mesh and hypergraph partitioning, and sequential and parallel sparse matrix block ordering.

About libptscotch

Package license:

Summary: PT-SCOTCH: (Parallel) Static Mapping, Graph, Mesh and Hypergraph Partitioning, and Parallel and Sequential Sparse Matrix Ordering Package

About ptscotch

Package license:

Summary: PT-SCOTCH: (Parallel) Static Mapping, Graph, Mesh and Hypergraph Partitioning, and Parallel and Sequential Sparse Matrix Ordering Package

Current build status

Azure

Variant Status linux_64_mpimpich linux_64_mpiopenmpi linux_aarch64_mpimpich linux_aarch64_mpiopenmpi linux_ppc64le_mpimpich linux_ppc64le_mpiopenmpi osx_64_mpimpich osx_64_mpiopenmpi osx_arm64_mpimpich osx_arm64_mpiopenmpi win_64

Current release info

Name	Downloads	Version	Platforms

Installing scotch-pkgs

Installing scotch-pkgs from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, libptscotch, libscotch, ptscotch, scotch can be installed with conda:

conda install libptscotch libscotch ptscotch scotch

or with mamba:

mamba install libptscotch libscotch ptscotch scotch

It is possible to list all of the versions of libptscotch available on your platform with conda:

conda search libptscotch --channel conda-forge

or with mamba:

mamba search libptscotch --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search libptscotch --channel conda-forge

# List packages depending on `libptscotch`:
mamba repoquery whoneeds libptscotch --channel conda-forge

# List dependencies of `libptscotch`:
mamba repoquery depends libptscotch --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating scotch-pkgs-feedstock

If you would like to improve the scotch-pkgs recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/scotch-pkgs-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @SylvainCorlay
• @Tobias-Fischer
• @basnijholt
• @dalcinl
• @davidbrochart
• @matthiasdiener
• @minrk

scotch-feedstock's Issues

rerender?

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

$ conda info

@conda-forge-admin, please rerender

split static libs into packages

Now that we are building shared libs (#27), we can shrink the package to only include the shared libs and not the static libs to avoid wasted space. Static libs can be available explicitly in [pt]scotch-static outputs.

build shared libs

It would be nice to build scotch as shared libs (cf conda-forge/mumps-feedstock#13)

as with mumps, debian patches may be of use for reference.

scotch recipe includes metis.h, conflicting with metis itself

scotch installs a metis.h, which I think is meant as a fallback mechanism.

I propose moving this to include/scotch/metis.h or just removing it, so it's not conflicting with the 'real' metis package.

run_exports with lib*** packages instead of normal packages?

Comment:

Recent build of mumps have the following warnings:

2023-12-01T11:05:35.1224077Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): Needed DSO lib/libptesmumps.so found in ['libptscotch']
2023-12-01T11:05:35.1225484Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): .. but ['libptscotch'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
2023-12-01T11:05:35.1237300Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): Needed DSO lib/libptscotch.so.7.0.2 found in ['libptscotch']
2023-12-01T11:05:35.1241256Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): .. but ['libptscotch'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
2023-12-01T11:05:35.1253236Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): Needed DSO lib/libptscotcherr.so found in ['libptscotch']
2023-12-01T11:05:35.1254654Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): .. but ['libptscotch'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
2023-12-01T11:05:35.1303272Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): Needed DSO lib/libscotch.so.7.0.2 found in ['libscotch']
2023-12-01T11:05:35.1304815Z WARNING (mumps-mpi,lib/libsmumps-5.2.1.so): .. but ['libscotch'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)

See for example https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/834445/logs/63 . Perhaps we should run_exports the dependending on lib** packages instead of the dependency on non-lib packages here?

Simultaneous scotch613 migration to the scotch702 migration

Comment:

It seems that there are two simultaneous migrations for scotch.

Are both necessary? Can we close one?

FYI: The 702 one seems to be stuck on nepr
https://github.com/conda-forge/neper-feedstock/pulls

VERSION fields in header are wrong for cross-compiled scotch.h since switch to cmake

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

The version strings in scotch.h are wrong since the switch to cmake, producing:

/*+ Version flags. +*/

#if ((! defined LIB_SCOTCH_H_UNIQUE) && (! defined SCOTCH_RENAME_ALL))
#define SCOTCH_VERSION SCOTCH_VERSION_NUM
#define SCOTCH_RELEASE SCOTCH_RELEASE_NUM
#define SCOTCH_PATCHLEVEL SCOTCH_PATCHLEVEL_NUM

which should be:

/*+ Version flags. +*/

#if ((! defined LIB_SCOTCH_H_UNIQUE) && (! defined SCOTCH_RENAME_ALL))
#define SCOTCH_VERSION 7
#define SCOTCH_RELEASE 0
#define SCOTCH_PATCHLEVEL 4

It appears only cross-compiled builds are affected, which suggests our dummysizes cmake workaround is where a fix is needed, possibly because it is missing these lines:

set(SCOTCH_VERSION 7)
set(SCOTCH_RELEASE 0)
set(SCOTCH_PATCHLEVEL 4)
set(SCOTCH_CODENAME "Sankara")

add_definitions(-DSCOTCH_VERSION_NUM=${SCOTCH_VERSION}
  -DSCOTCH_RELEASE_NUM=${SCOTCH_RELEASE}
  -DSCOTCH_PATCHLEVEL_NUM=${SCOTCH_PATCHLEVEL})

Installed packages

# packages in environment at /Users/minrk/conda/envs/scotch:
#
# Name                    Version                   Build  Channel
bzip2                     1.0.8                h93a5062_5    conda-forge
libcxx                    16.0.6               h4653b0c_0    conda-forge
libgfortran               5.0.0           13_2_0_hd922786_1    conda-forge
libgfortran5              13.2.0               hf226fd6_1    conda-forge
libptscotch               7.0.4                h5340af2_0    conda-forge
libscotch                 7.0.4                hc938e73_0    conda-forge
libzlib                   1.2.13               h53f4e23_5    conda-forge
llvm-openmp               17.0.6               hcd81f8e_0    conda-forge
mpi                       1.0                       mpich    conda-forge
mpich                     4.1.2              hd4b5bf3_100    conda-forge
ptscotch                  7.0.4                heaa5b5c_0    conda-forge
scotch                    7.0.4                heaa5b5c_0    conda-forge
xz                        5.2.6                h57fd34a_0    conda-forge
zlib                      1.2.13               h53f4e23_5    conda-forge

Environment info

mamba version : 1.5.2
     active environment : None
            shell level : 0
       user config file : /Users/minrk/.condarc
 populated config files : /Users/minrk/conda/.condarc
                          /Users/minrk/.condarc
          conda version : 23.9.0
    conda-build version : 3.27.0
         python version : 3.10.13.final.0
       virtual packages : __archspec=1=m1
                          __osx=14.1.2=0
                          __unix=0=0
       base environment : /Users/minrk/conda  (writable)
      conda av data dir : /Users/minrk/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/minrk/conda/pkgs
                          /Users/minrk/.conda/pkgs
       envs directories : /Users/minrk/conda/envs
                          /Users/minrk/.conda/envs
               platform : osx-arm64
             user-agent : conda/23.9.0 requests/2.31.0 CPython/3.10.13 Darwin/23.1.0 OSX/14.1.2 solver/libmamba conda-libmamba-solver/23.9.3 libmambapy/1.5.2
                UID:GID : 501:20
             netrc file : /Users/minrk/.netrc
           offline mode : False