8000 site.cfg.example should not reference blas_opt and lapack_opt · numpy/numpy@ffd4332 · GitHub
[go: up one dir, main page]
Skip to content

Commit ffd4332

Browse files
ogriselogrisel
committed
site.cfg.example should not reference blas_opt and lapack_opt
blas_opt and lapack_opt sections are not actually read by the numpy.distutils.system_info machinery. They are just meta entry points for the `get_info` public function that in turns introspec the atlas, openblas and mkl sections.
1 parent 43fcc0e commit ffd4332

File tree

1 file changed

+34
-52
lines changed

1 file changed

+34
-52
lines changed

‎site.cfg.example

Lines changed: 34 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -63,48 +63,46 @@
6363
#library_dirs = /usr/local/lib
6464
#include_dirs = /usr/local/include
6565

66-
# Optimized BLAS and LAPACK
67-
# -------------------------
68-
# Use the blas_opt and lapack_opt sections to give any settings that are
69-
# required to link against your chosen BLAS and LAPACK, including the regular
70-
# FORTRAN reference BLAS and also ATLAS. Some other sections still exist for
71-
# linking against certain optimized libraries (e.g. [atlas], [lapack_atlas]),
72-
# however, they are now deprecated and should not be used.
73-
#
74-
# These are typical configurations for ATLAS (assuming that the library and
75-
# include directories have already been set in [DEFAULT]; the include directory
76-
# is important for the BLAS C interface):
77-
#
78-
#[blas_opt]
79-
#libraries = f77blas, cblas, atlas
80-
#
81-
#[lapack_opt]
82-
#libraries = lapack, f77blas, cblas, atlas
83-
#
84-
# If your ATLAS was compiled with pthreads, the names of the libraries might be
85-
# different:
86-
#
87-
#[blas_opt]
88-
#libraries = ptf77blas, ptcblas, atlas
89-
#
90-
#[lapack_opt]
91-
#libraries = lapack, ptf77blas, ptcblas, atlas
92-
66+
# Atlas
67+
# -----
68+
# Atlas is an open source optimized implementation of the BLAS and Lapack
69+
# routines. Numpy will try to build against Atlas by default when available in
70+
# the system library dirs. To build numpy against a custom installation of
71+
# Atlas you can add an explicit section such as the following. Here we assume
72+
# that Atlas was configured with ``prefix=/opt/atlas``.
73+
#
74+
# [atlas]
75+
# library_dirs = /opt/atlas/lib
76+
# include_dirs = /opt/atlas/include
9377

94-
# Openblas
78+
# OpenBLAS
9579
# --------
96-
# If you choose to use openblas, then use this section instead of the above,
97-
# adjusting as needed for your configuration. You may need to set the LAPACK
98-
# and BLAS environmental variables to point to your openblas static library.
99-
# E.g., export BLAS=/path/to/libopenblas.a
100-
# export LAPACK=/path/to/libopenblas.a
80+
# OpenBLAS is another open source optimized implementation of BLAS and Lapack
81+
# and can be seen as an alternative to Atlas. To build numpy against OpenBLAS
82+
# instead of Atlas, use this section instead of the above, adjusting as needed
83+
# for your configuration (in the following example we installed OpenBLAS with
84+
# ``make install PREFIX=/opt/openblas``.
10185
#
10286
# [openblas]
10387
# libraries = openblas
104-
#
105-
# [lapack_opt]
106-
# libraries = openblas
88+
# library_dirs = /opt/openblas/lib
89+
# include_dirs = /opt/openblas/include
10790

91+
# MKL
92+
#----
93+
# MKL is Intel's very optimized yet proprietary implementation of BLAS and
94+
# Lapack.
95+
# For recent (9.0.21, for example) mkl, you need to change the names of the
96+
# lapack library. Assuming you installed the mkl in /opt, for a 32 bits cpu:
97+
# [mkl]
98+
# library_dirs = /opt/intel/mkl/9.1.023/lib/32/
99+
# lapack_libs = mkl_lapack
100+
#
101+
# For 10.*, on 32 bits machines:
102+
# [mkl]
103+
# library_dirs = /opt/intel/mkl/10.0.1.014/lib/32/
104+
# lapack_libs = mkl_lapack
105+
# mkl_libs = mkl, guide
108106

109107
# UMFPACK
110108
# -------
@@ -125,7 +123,6 @@
125123
#[umfpack]
126124
#umfpack_libs = umfpack
127125

128-
129126
# FFT libraries
130127
# -------------
131128
# There are two FFT libraries that we can configure here: FFTW (2 and 3) and djbfft.
@@ -143,18 +140,3 @@
143140
#[djbfft]
144141
#include_dirs = /usr/local/djbfft/include
145142
#library_dirs = /usr/local/djbfft/lib
146-
147-
148-
# MKL
149-
#----
150-
# For recent (9.0.21, for example) mkl, you need to change the names of the
151-
# lapack library. Assuming you installed the mkl in /opt, for a 32 bits cpu:
152-
# [mkl]
153-
# library_dirs = /opt/intel/mkl/9.1.023/lib/32/
154-
# lapack_libs = mkl_lapack
155-
#
156-
# For 10.*, on 32 bits machines:
157-
# [mkl]
158-
# library_dirs = /opt/intel/mkl/10.0.1.014/lib/32/
159-
# lapack_libs = mkl_lapack
160-
# mkl_libs = mkl, guide

0 commit comments

Comments
 (0)
0