Compile-belt - Revision history

Lothar.brendel: /* makefile_user_machinedefs */ typo

2026-04-02T14:06:50Z

makefile_user_machinedefs: typo

← Older revision		Revision as of 16:06, 2 April 2026
Line 74:		Line 74:
	* <code>BELT_DIR = $(HOME)/belt</code> <ref name="path"> Adjust to your chosen location.</ref>		* <code>BELT_DIR = $(HOME)/belt</code> <ref name="path"> Adjust to your chosen location.</ref>
	* <code>PETSC_DIR = $(HOME)/petsc-3.1-p8</code> <ref name="path"> Adjust to your chosen location.</ref>		* <code>PETSC_DIR = $(HOME)/petsc-3.1-p8</code> <ref name="path"> Adjust to your chosen location.</ref>
	* <code>PETSC_ARCH =</code> your ~~Choice~~ from PETSc's [[#setting up the configuration\|configuration step]] above		* <code>PETSC_ARCH =</code> your choice from PETSc's [[#setting up the configuration\|configuration step]] above
	* <code>PETSC_LAPACK = lapack</code>		* <code>PETSC_LAPACK = lapack</code>
	* <code>PETSC_BLAS = blas</code>		* <code>PETSC_BLAS = blas</code>

Lothar.brendel: /* Python 2 */ miniconda3 needs the internet

2026-04-02T14:03:47Z

Python 2: miniconda3 needs the internet

← Older revision		Revision as of 16:03, 2 April 2026
Line 23:		Line 23:

	# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.		# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.
	# As an alternative, install [https://www.anaconda.com/docs/getting-started/miniconda/main miniconda] into your $HOME and create a Python 2.7 environment: <code>conda create -n py27 python=2.7</code> (will consume about 1GB). Don't install anything else into this environment. (Because the package ''binutils'' may be pulled in; it provides the miniconda version of the linker <code>ld</code>, which may later confuse <code>make</code>.)		# As an alternative (if there is free access to the internet), install [https://www.anaconda.com/docs/getting-started/miniconda/main miniconda] into your $HOME and create a Python 2.7 environment: <code>conda create -n py27 python=2.7</code> (will consume about 1GB). Don't install anything else into this environment. (Because the package ''binutils'' may be pulled in; it provides the miniconda version of the linker <code>ld</code>, which may later confuse <code>make</code>.)

Lothar.brendel: /* Python 2 */ wording

2026-04-02T13:59:48Z

Python 2: wording

← Older revision		Revision as of 15:59, 2 April 2026
Line 20:		Line 20:
	== Python 2 ==		== Python 2 ==

	''belt'' ~~needs~~ an old PETSc version, namely [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz 3.1-p8] from March 2011. That version needs Python < 3 for its configuration, with the last version (Python 2.7.18) having been discontinued in 2020 and dropped from the major Linux distros around 2024. If there is really no Python 2 on the machine, two possible solutions<ref>The most lightweight variant would be to get a [https://git.sr.ht/~knazarov/static-python statically built python]2.7 binary to work, or at least a [https://pypi.org/project/portable-python portable] one.</ref> are:		''belt'' uses an old PETSc version, namely [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz 3.1-p8] from March 2011. That version needs Python < 3 for its configuration, with the last version (Python 2.7.18) having been discontinued in 2020 and dropped from the major Linux distros around 2024. If there is really no Python 2 on the machine, two possible solutions<ref>The most lightweight variant would be to get a [https://git.sr.ht/~knazarov/static-python statically built python]2.7 binary to work, or at least a [https://pypi.org/project/portable-python portable] one.</ref> are:

	# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.		# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.

Lothar.brendel: /* adjustments on specific computers */ +amplitude

2026-04-02T13:58:20Z

adjustments on specific computers: +amplitude

← Older revision		Revision as of 15:58, 2 April 2026
Line 90:		Line 90:

	= adjustments on specific computers =		= adjustments on specific computers =

			== amplitUDE ==

			=== PETSc configuration ===

			==== Intel compiler + Intel MPI ====

			The necessary modules need to be loaded, which can be done in the configuration script:

			<syntaxhighlight lang="shell">
			module -s load compiler/2024.0.0
			module -s load mkl/2024.0
			module -s load mpi # sets I_MPI_ROOT
			</syntaxhighlight>

			And the Python-line becomes:

			<syntaxhighlight lang="shell">
			python2 ./config/configure.py PETSC_ARCH=amplitude_intel_impi \
			--CFLAGS='' \
			--COPTFLAGS=-O3 --FOPTFLAGS=-O3 \
			--with-mpi-dir=$I_MPI_ROOT \
			--with-blas-lib=[libmkl_intel_lp64.a,libmkl_sequential.a,libmkl_core.a] --with-lapack-lib=libmkl_core.a \
			--with-x=0 --with-debugging=0
			</syntaxhighlight>

			=== making PETSc ===

			* Before executing the <code>make PETSC_DIR=</code>... <code>all</code>-line, the three modules from above have to be loaded.
			* <code>make PETSC_DIR=</code>... <code>test</code> will fail when carried out on the login node due to a warning message. That failure can be ignored.

			=== makefile_user_machinedefs ===

			Values differing from above:

			* <code>FC = mpif90</code>
			* <code>PETSC_ARCH = amplitude_intel_impi</code>
			* <code>PETSC_LAPACK = mkl_core</code>
			* <code>PETSC_BLAS = mkl_intel_lp64 -lmkl_sequential</code>

			== other ==

	(to be continued)		(to be continued)

Lothar.brendel: /* making PETSc */ make-line

2026-03-24T17:17:17Z

making PETSc: make-line

← Older revision		Revision as of 19:17, 24 March 2026
Line 64:		Line 64:
	= making PETSc =		= making PETSc =

	Copying and executing the line from above will <code>make</code> PETSc, i.e. compile the library (which takes some time). A successful <code>make</code> will terminate with printing the same line, except <code>all</code>→<code>test</code>. Copying and executing it, will perform three tests.		Copying and executing the <code>make</code>-line from above will <code>make</code> PETSc, i.e. compile the library (which takes some time). A successful <code>make</code> will terminate with printing the same line, except <code>all</code>→<code>test</code>. Copying and executing it will perform three tests.

	= makefile_user_machinedefs =		= makefile_user_machinedefs =

Lothar.brendel: /* setting up the configuration */ settings

2026-03-24T17:15:32Z

setting up the configuration: settings

← Older revision		Revision as of 19:15, 24 March 2026
Line 58:		Line 58:
	--with-x=0 --with-debugging=0		--with-x=0 --with-debugging=0
	</syntaxhighlight>		</syntaxhighlight>
	The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Several versions of PETSc ~~(using e.g. a~~ different ~~MPI)~~ can be kept simultaneously and chosen later in the [[#makefile_user_machinedefs\|makefile_user_machinedefs]]. Running the script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but ~~that~~ will be outdated versions and will be compiled from source.</ref> and will finish with printing a line <code>make PETSC_DIR=</code>...<code> all</code>.		The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Several versions of PETSc with different settings can be kept simultaneously and chosen later in the [[#makefile_user_machinedefs\|makefile_user_machinedefs]]. Running the script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but those will be outdated versions and will be compiled from source.</ref> and will finish with printing a line <code>make PETSC_DIR=</code>...<code> all</code>.

	<references />		<references />

Lothar.brendel: making PETSc, makefile_user_machinedefs, making belt

2026-03-24T17:12:39Z

making PETSc, makefile_user_machinedefs, making belt

@@ Line 24: / Line 24: @@
 # Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.
 # As an alternative, install [https://www.anaconda.com/docs/getting-started/miniconda/main miniconda] into your $HOME and create a Python 2.7 environment: <code>conda create -n py27 python=2.7</code> (will consume about 1GB). Don't install anything else into this environment. (Because the package ''binutils'' may be pulled in; it provides the miniconda version of the linker <code>ld</code>, which may later confuse <code>make</code>.)
 = configuring PETSc =
@@ Line 55: / Line 58: @@
          --with-x=0 --with-debugging=0
 </syntaxhighlight>
-The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Running this script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but that will be outdated versions and will be compiled from source.</ref> and will finish with printing a line <code>make PETSC_DIR=</code>...<code> all</code>.
+The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Several versions of PETSc (using e.g. a different MPI) can be kept simultaneously and chosen later in the [[#makefile_user_machinedefs|makefile_user_machinedefs]]. Running the script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but that will be outdated versions and will be compiled from source.</ref> and will finish with printing a line <code>make PETSC_DIR=</code>...<code> all</code>.
-== making PETSc ==
+(to be continued)
-Copying and executing the line from above will <code>make</code> PETSc, i.e. compile the library (which takes some time). A successful <code>make</code> will terminate with printing the same line, except <code>all</code>→<code>test</code>. Copying and executing it will perform three tests.
+----
-= To be [[Talk:Compile-belt|patrolled]], yet =
+= almost obsolete =
 (and to be converted from [https://en.wikipedia.org/wiki/Markdown Markdown] to [https://en.wikipedia.org/wiki/Help:Wikitext Wikitext])

Lothar.brendel: /* setting up the configuration */ +make

2026-03-24T15:48:45Z

setting up the configuration: +make

← Older revision		Revision as of 17:48, 24 March 2026
Line 55:		Line 55:
	--with-x=0 --with-debugging=0		--with-x=0 --with-debugging=0
	</syntaxhighlight>		</syntaxhighlight>
	The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Running this script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but that will be outdated versions and will be compiled from source.</ref> and will finish with a line <code>make PETSC_DIR=</code>... ~~to be copied and executed~~.		The value for <code>PETSC_ARCH</code> can be chosen freely, you'll probably put something more meaningful than ''my_arch'', like e.g. ''Debian_MPICH'' if that is your distro and chosen MPI. Running this script will find BLAS/LAPACK and the chosen MPI <ref>If not, it will suggest to add options to download them, but that will be outdated versions and will be compiled from source.</ref> and will finish with printing a line <code>make PETSC_DIR=</code>...<code> all</code>.

	(~~to be continued~~)		== making PETSc ==

			Copying and executing the line from above will <code>make</code> PETSc, i.e. compile the library (which takes some time). A successful <code>make</code> will terminate with printing the same line, except <code>all</code>→<code>test</code>. Copying and executing it will perform three tests.

	= To be [[Talk:Compile-belt\|patrolled]], yet =		= To be [[Talk:Compile-belt\|patrolled]], yet =

Lothar.brendel: /* Python 2 */ 3 -> footnote

2026-03-23T07:04:20Z

Python 2: 3 -> footnote

← Older revision		Revision as of 09:04, 23 March 2026
Line 20:		Line 20:
	== Python 2 ==		== Python 2 ==

	''belt'' needs an old PETSc version, namely [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz 3.1-p8] from March 2011. That version needs Python < 3 for its configuration, with the last version (Python 2.7.18) having been discontinued in 2020 and dropped from the major Linux distros around 2024. If there is really no Python 2 on the machine, two possible solutions are:		''belt'' needs an old PETSc version, namely [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz 3.1-p8] from March 2011. That version needs Python < 3 for its configuration, with the last version (Python 2.7.18) having been discontinued in 2020 and dropped from the major Linux distros around 2024. If there is really no Python 2 on the machine, two possible solutions<ref>The most lightweight variant would be to get a [https://git.sr.ht/~knazarov/static-python statically built python]2.7 binary to work, or at least a [https://pypi.org/project/portable-python portable] one.</ref> are:

	# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.		# Download [https://downloads.python.org/pypy/pypy2.7-v7.3.20-linux64.tar.bz2 pypy2.7], extract it to a suitable location in your $HOME (will consume about 130MB) and use <code>pypy2.7-v*-linux64/bin/python2</code> as Python interpreter.
	# As an alternative, install [https://www.anaconda.com/docs/getting-started/miniconda/main miniconda] into your $HOME and create a Python 2.7 environment: <code>conda create -n py27 python=2.7</code> (will consume about 1GB). Don't install anything else into this environment. (Because the package ''binutils'' may be pulled in; it provides the miniconda version of the linker <code>ld</code>, which may later confuse <code>make</code>.)		# As an alternative, install [https://www.anaconda.com/docs/getting-started/miniconda/main miniconda] into your $HOME and create a Python 2.7 environment: <code>conda create -n py27 python=2.7</code> (will consume about 1GB). Don't install anything else into this environment. (Because the package ''binutils'' may be pulled in; it provides the miniconda version of the linker <code>ld</code>, which may later confuse <code>make</code>.)
	# (The most lightweight variant would be to get a [https://git.sr.ht/~knazarov/static-python statically built python]2.7 binary to work, or at least a [https://pypi.org/project/portable-python portable] one.)

	= configuring PETSc =		= configuring PETSc =

Lothar.brendel: /* extracting and patching PETSc */ -py2.7

2026-03-20T22:40:59Z

extracting and patching PETSc: -py2.7

← Older revision		Revision as of 00:40, 21 March 2026
Line 31:		Line 31:

	# Extract [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz petsc-3.1-p8] into a suitable location in your $HOME.		# Extract [https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.1-p8.tar.gz petsc-3.1-p8] into a suitable location in your $HOME.
	# ~~Even with Python 2 being available~~, PETSc's C-code and the configuration scripts need a bit of [https://en.wikipedia.org/wiki/Patch_(Unix) patching]: Save the [[:Media:Petsc.patch\|petsc.patch]] into the PETSc folder.		# Since it's old, PETSc's C-code and the configuration scripts need a bit of [https://en.wikipedia.org/wiki/Patch_(Unix) patching]: Save the [[:Media:Petsc.patch\|petsc.patch]] into the PETSc folder.

	== setting up the configuration ==		== setting up the configuration ==