virtual/{{c,}blas,lapack{,e}}: replaced by counterparts in ::gentoo.

sci-libs/{{c,}blas,lapack{,e}}-reference: Remove. Remove BLAS/LAPACK migration scripts. Remove outdated documentation on BLAS/LAPACK. Update README.md to point to the new framework in ::gentoo. Reference: https://wiki.gentoo.org/wiki/Blas-lapack-switch Closes: https://github.com/gentoo/sci/issues/805 Closes: https://github.com/gentoo/sci/issues/926 Closes: https://github.com/gentoo/sci/issues/734 Closes: https://github.com/gentoo/sci/issues/897 Closes: https://github.com/gentoo/sci/issues/925 Package-Manager: Portage-2.3.69, Repoman-2.3.12 Signed-off-by: Benda Xu <heroxbd@gentoo.org>
3 years ago · e105f0f6a2
51 changed files with 4 additions and 3929 deletions
--- a/README.md
+++ b/README.md
@ -14,16 +14,11 @@ wget https://gitweb.gentoo.org/proj/sci.git/plain/metadata/science.conf -O /etc/

 To start using the overlay you now only need to get the ebuilds, via `emerge --sync`.

-### BLAS and LAPACK Migration
+### BLAS and LAPACK

-There is a long-standing BLAS and LAPACK stack incompatibility between the Science Overlay and the Base Gentoo Overlay.
-A fix [is being considered](https://github.com/gentoo/sci/issues/805), bit is still not scheduled for implementation.
-In the mean time, the most automated and up-to-date solution (building on [the original one](https://wiki.gentoo.org/wiki/User_talk:Houseofsuns)) is to run (as root, and after having installed the overlay):
-
-```
-cd ${EPREFIX}/var/lib/overlays/science/scripts
-./lapack-migration.sh
-```
+[The BLAS and LAPACK switching framework](https://wiki.gentoo.org/wiki/Blas-lapack-switch)
+in ::gentoo has been implemented. The Science overlay will no longer
+carry blas and lapack ebuilds.

 ### Uninstall

--- a/docs/proj/blas-lapack.xml
+++ b/docs/proj/blas-lapack.xml
@ -1,492 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-
-<guide link="/proj/en/science/blas-lapack.xml">
-<title>Using multiple versions of BLAS and LAPACK with Gentoo/Linux</title>
-
-<author title="Author">
-  <mail link="bicatali@gentoo.org">Sébastien Fabbro</mail>
-</author>
-<author title="Author">
-  <mail link="markusle@gentoo.org">Markus Dittrich</mail>
-</author>
-<author title="Editor">
-  <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
-</author>
-
-<abstract>
-This guide explains the use of the different implementations of the BLAS
-and LAPACK libraries that are available via Portage.
-</abstract>
-
-<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<license/>
-
-<version>1.0</version>
-<date>2007-10-22</date>
-
-<chapter>
-<title>Introduction</title>
-<section>
-<body>
-
-<p>
-The Basic Linear Algebra Subroutines (BLAS) and Linear Algebra PACKage (LAPACK)
-are well designed linear algebra software libraries developed by the
-High Performance Computing (HPC) community. BLAS
-implements dense matrix and vectors products, while LAPACK provides routines for 
-solving systems of linear equations. Both are widely used in
-many scientific applications and it is, therefore, important to 
-have efficient implementations available.
-</p>
-
-<p>
-Originally written in FORTRAN 77, a number of additional language
-wrappers have been developed for languages like C, C++, FORTRAN 95, and others.
-The following legacy libraries are available via the reference ebuilds:
-</p>
-
-<ul>
-  <li>
-    <uri link="http://netlib.org/blas">BLAS</uri>: FORTRAN 77 implementation of
-    BLAS
-  </li>
-  <li>
-    <uri link="http://netlib.org/blas">CBLAS</uri>: C implementation of BLAS
-  </li>
-  <li>
-    <uri link="http://netlib.org/lapack">LAPACK</uri>: FORTRAN 77 implementation
-    of LAPACK
-  </li>
-</ul>
-
-<p>
-In addition, Gentoo provides a number of optimized BLAS and LAPACK implementations
-that will be described below. Different implementations are bundled together with
-Gentoo's <c>eselect</c> system and the widely used <c>pkg-config</c> tool.
-</p>
-
-<p> It is important to note that if you require, e.g., a well performing 
-BLAS implementation, simply emerging X over Y often is not enough. Rather, you will have
-to carefully benchmark your applications since performance may depend 
-on many factors,
-such as hardware or network.
-If you are simply looking for a well performing and well tested
-implementation, the reference ebuilds will likely be your best choice.
-</p>
-
-
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>For Users</title>
-<section>
-<title>Installing</title>
-<body>
-
-<p>
-If best possible performance is not of paramount importance for you 
-and you simply
-need BLAS and/or LAPACK, just emerge the virtual packages:
-</p>
-
-<pre caption="Installing">
-# <i>emerge blas cblas lapack</i>
-</pre>
-
-<p>
-These will install the reference legacy	packages from
-<uri>http://netlib.org</uri>. They are well tested, easy to debug
-implementations. They should satisfy most users; if they're all you need, you're
-done reading.
-</p>
-
-<p>
-However, if:
-</p>
-
-<ul>
-  <li>BLAS/LAPACK are critical for the speed of your applications</li>
-  <li>you absolutely need to build the fastest computer</li>
-  <li>you want to help Gentoo sci project to improve their packages</li>
-</ul>
-
-<p>
-... then read on, and be sure to file bugs both to Gentoo and upstream.
-</p>
-
-<p>
-There is a number of optimized implementations of these libraries in the Portage
-tree:
-</p>
-
-<ul>
-  <li>
-   <uri link="http://math-atlas.sourceforge.net">ATLAS</uri>: Automatically
-   Tuned Linear Algebra Software is an open-source package that empirically
-   tunes the library to the machine it is being compiled on. It provides BLAS
-   (FORTRAN 77 and C), and LAPACK implementations on various architectures.
-  </li>
-  <li>
-   <uri
-   link="http://www.tacc.utexas.edu/resources/software/software.php">GotoBLAS</uri>:
-   Goto BLAS provide open-source, free for academic use, hand-coded
-   machine language, processor optimized versions of the FORTRAN 77 BLAS
-   routines. Claims to be the fastest BLAS.
-  </li>
-  <li>
-    <uri link="http://developer.intel.com/software/products/mkl/">MKL</uri>:
-    Intel® Math Kernel Library is a closed-source but free package for
-    non-commercial use containing BLAS (FORTRAN 77 and C), LAPACK optimized for
-    Intel® based architectures: x86, amd64 and ia64.
-  </li>
-</ul>
-
-<p>
-Usually performance gain is noticeable mainly with BLAS, since LAPACK routines
-depend on BLAS kernels.
-</p>
-
-</body>
-</section>
-<section>
-<title>Compiling and linking with installed libraries</title>
-<body>
-
-<p>
-We took great care to make sure that each package provides consistent pkg-config files.
-Hence, compiling and linking with BLAS/LAPACK should be simple and straightforward:
-</p>
-
-<pre caption="Compiling and linking BLAS/LAPACK">
-# <i>pkg-config --libs blas</i>    <comment>(To link with FORTRAN 77 BLAS library)</comment>
-# <i>pkg-config --cflags cblas</i> <comment>(To compile against C BLAS library)</comment>
-# <i>pkg-config --libs cblas</i>   <comment>(To link with C BLAS library)</comment>
-# <i>pkg-config --libs lapack</i>  <comment>(To link with FORTRAN 77 LAPACK library)</comment>
-</pre>
-
-<p>
-<c>pkg-config</c> files are available for whichever implementation you select with <c>eselect</c>.
-More information on using <c>pkg-config</c> can be obtained with <c>man pkg-config</c>. 
-</p>
-
-</body>
-</section>
-<section>
-<title>Choosing libraries</title>
-<body>
-
-<p>
-You can easily switch BLAS, CBLAS and LAPACK implementations with
-<c>eselect</c>. At this point, you probably have <c>eselect-blas</c>,
-<c>eselect-cblas</c> and <c>eselect-lapack</c> installed. If you do not,
-install them now! Using eselect, you can view which implementations of CBLAS
-are available.
-</p>
-
-<pre caption="Viewing available implementations">
-# <i>eselect cblas list</i>
-Installed CBLAS for library directory lib64
-[1]   atlas
-[2]   atlas-threads
-[3]   gsl
-[4]   mkl-threads *
-[5]   reference
-</pre>
-
-<p>
-The implementation marked with an asterisk (*) is the currently
-selected implementation. To switch implementations, run:
-</p>
-
-<pre caption="Switching to the ATLAS implementation of LAPACK">
-# <i>eselect lapack set atlas</i>
-</pre>
-
-<p>
-To learn more about the <c>eselect</c> tool, visit the 
-<uri link="http://www.gentoo.org/proj/en/eselect/user-guide.xml">eselect guide</uri>
-</p>
-
-<p>
-When selecting blas, cblas or lapack profiles try to avoid mixing
-different implementations since we don't have any mechanism to enforce
-reasonable profiles. However, here is a list of well performing
-profile combinations that have been used successfully in the past:
-</p>
-<ul>
-  <li> Most CPUs:
-    <ul>
-      <li>blas,cblas: atlas (or atlas-threads with multi-processor)</li>
-      <li>lapack:atlas</li>
-    </ul>
-  </li>
-  <li> Most CPUs:
-    <ul>
-      <li>blas: goto </li>
-      <li>cblas,lapack: reference</li>
-    </ul>
-  </li>
-  <li> AMD based CPUs:
-    <ul>
-      <li>cblas: reference</li>
-    </ul>
-  </li>
-  <li> Intel based CPUs:
-    <ul>
-      <li>blas,cblas,lapack: mkl-threads</li>
-    </ul>
-  </li>
-</ul>
-
-</body>
-</section>
-
-<section>
-<title>Choosing a compiler</title>
-<body>
-
-<p>
-Most of the libraries can compile with both the GNU compiler collection and the
-Intel® compilers on the x86, amd64 and ia64 architectures. By default, you are
-probably using <c>gcc</c>. You can also compile the <c>*-reference</c> packages
-with <c>ifort</c> and <c>icc</c>. To do this, you need to define the F77
-environment variable and don't forget the FFLAGS.
-</p>
-
-<pre caption="Using non-GCC compilers">
-# <i>F77=ifort FFLAGS="-O2 -mp" emerge blas-reference</i>
-</pre>
-
-<p>
-Depending on your hardware, a small performance gain can be noticed thanks to
-vectorization. The <c>-mp</c> flag maintains floating-point precision, since by
-default ifort is pretty aggressive on floating point arithmetic, and we are
-actually compiling a math package. Try <c>man ifort</c> to see additional flags
-to fit your hardware.
-</p>
-
-<p>
-Some of the implementations let you specify the Intel® C compiler as
-well. Please beware that not all libraries compile with all
-combinations.  You should receive an error during the emerge in case you have
-chosen an incompatible combination.
-</p>
-
-<p>
-As usual for Gentoo, there are many combinations of USE flags and
-compilers with which you could compile a package. Unfortunately
-switching compilers between BLAS and LAPACK might not be always
-compatible. For example: 
-</p>
-
-<pre caption="Incompatible combinations">
-# <i>F77=gfortran FFLAGS="-O2" emerge lapack-reference</i>
-</pre>
-
-<p>
-This will most likely break things or not even compile.
-</p>
-
-<p>
-Try to be consistent in your choice. Stay with the GCC most of the time will
-avoid you some trouble, unless you want to use the MKL, in which case the Intel®
-C and FORTRAN compilers make a good combination.
-</p>
-
-</body>
-</section>
-<section>
-<title>Documentation</title>
-<body>
-
-<p>
-If you need BLAS or LAPACK to develop your own programs, the documentation
-becomes pretty handy. Setting the USE="doc" flag for the corresponding BLAS or
-LAPACK package will install man pages and quick reference sheets from the
-<c>app-doc/blas-docs</c> and <c>app-doc/lapack-docs</c> packages. They are
-standard and valid for all implementations. For optimized packages, the
-USE="doc" flags will usually install extra doc in PDF or HTML format.
-</p>
-
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>For Developers</title>
-<section>
-<title>Providing new implementations</title>
-<body>
-
-<p>
-The Portage tree contains many ebuilds that depend on the BLAS/CBLAS/LAPACK
-libraries. As there is more than one possible implementation, the Gentoo
-Scientific Project reorganized all the packages to provide <c>virtual/blas</c>,
-<c>virtual/cblas</c>, and <c>virtual/lapack</c>. All ebuilds using BLAS should
-depend on this virtual package, unless it is explicitly known to break with
-different BLAS implementations.
-</p>
-
-<p>
-To work with Gentoo's configuration tools
-<c>app-admin/eselect-{blas,cblas,lapack}</c>, and the virtual, every ebuild that
-installs a BLAS implementation must fulfill following requirements:
-</p>
-
-<ol>
-  <li>
-    The ebuild must install an eselect file for each profile it provides. The
-    libraries should link to the ones in <path>/usr/$(get_libdir)</path>
-    directories and the include files in <path>/usr/include</path>:
-    <ul>
-      <li>
-	<path>libblas.so[.0]</path> - Shared object for FORTRAN BLAS
-	applications
-      </li>
-      <li>
-        <path>libblas.a</path> - Static library for FORTRAN BLAS applications
-      </li>
-      <li>
-        <path>libcblas.so[.0]</path> - Shared object for C/C++ CBLAS applications
-      </li>
-      <li>
-        <path>libcblas.a</path> - Static library for C/C++ CBLAS applications
-      </li>
-      <li><path>cblas.h</path> - Include header for C/C++ applications</li>
-      <li>
-        <path>liblapack.so[.0]</path> - Shared object for FORTRAN LAPACK
-	applications
-      </li>
-      <li>
-        <path>liblapack.a</path> - Static library for FORTRAN LAPACK applications
-      </li>
-    </ul>
-  </li>
-  <li>
-    The ebuild must install a <path>blas.pc</path>, <path>cblas.pc</path> and/or
-    <path>lapack.pc</path> pkg-config file and therefore RDEPEND on
-    <c>dev-util/pkgconfig</c>.  They should also be included in the eselect
-    files, and link to the <path>/usr/$(get_libdir)/pkgconfig</path> directory:
-    <ul>
-      <li><path>blas.pc</path> - BLAS pkg-config file</li>
-      <li><path>cblas.pc</path> - CBLAS pkg-config file</li>
-      <li><path>lapack.pc</path> - LAPACK pkg-config file</li>
-    </ul>
-  </li>
-  <li>Be included in the virtual package as a possible provider:
-    <ul>
-      <li><c>virtual/blas</c> - BLAS virtual package</li>
-      <li><c>virtual/cblas</c> - CBLAS virtual package</li>
-      <li><c>virtual/lapack</c> - LAPACK virtual package</li>
-    </ul>
-  </li>
-</ol>
- 
-<p>
-The easiest way of understanding all this is probably getting inspiration from
-one of the available packages.  Currently the Portage tree provide the following
-virtuals:
-</p>
-
-<table>
-<tr>
-  <th>Package name</th>
-  <th>virtual/blas</th>
-  <th>virtual/cblas</th>
-  <th>virtual/lapack</th>
-</tr>
-<tr>
-  <ti><c>sci-libs/blas-atlas</c></ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/blas-goto</c></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/blas-reference</c></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/cblas-reference</c></ti>
-  <ti></ti>
-  <ti>*</ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/gsl</c></ti>
-  <ti></ti>
-  <ti>*</ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/lapack-atlas</c></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti>*</ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/lapack-reference</c></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti>*</ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/mkl</c></ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-</tr>
-</table>
-
-</body>
-</section>
-<section>
-<title>Packages with BLAS/LAPACK dependencies</title>
-<body>
-
-<p>
-Simply use <c>virtual/{blas,cblas,lapack}</c> as a [R]DEPEND. To build some
-packages, you might need to use the pkg-config tool. If you are lucky, the
-package uses autotools together with common BLAS and LAPACK M4 macros.In this
-case, the configuration step becomes simple. For example:
-</p>
-
-<pre caption="Sample package configuration">
-<keyword>econf</keyword> --with-blas="<var>$(pkg-config --libs blas)</var>"
-</pre>
-
-<impo>
-Don't forget to add <c>dev-util/pkgconfig</c> in DEPEND.
-</impo>
-
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>In the near future</title>
-<section>
-<body>
-
-<p>
-We plan to include more standard BLAS, LAPACK libraries: BLAS 95, LAPACK 95,
-Sparse BLAS, ScaLAPACK. If you feel inclined to write an ebuild for these, you
-are more than welcomed to file it on our <uri
-link="http://bugs.gentoo.org">Bugzilla</uri>.
-</p>
-
-</body>
-</section>
-</chapter>
-</guide>
--- a/docs/proj/index.xml
+++ b/docs/proj/index.xml
@ -55,7 +55,6 @@
  <subproject ref="/proj/en/science/physics/index.xml" />
  -->

-  <resource link="blas-lapack.xml">Guide on using BLAS/LAPACK</resource>
  <resource link="contrib.xml">Guide on contributing to the science project</resource>
  <resource link="http://overlays.gentoo.org/proj/science">Official overlay</resource>
  <resource link="http://news.gmane.org/gmane.linux.gentoo.science/">Mailing list archives</resource>
--- a/docs/proj/linalg.xml
+++ b/docs/proj/linalg.xml
@ -1,530 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-
-<guide link="/proj/en/science/linalg.xml">
-<title>Linear Algebra on Gentoo</title>
-
-<author title="Author">
-  <mail link="bicatali@gentoo.org">Sébastien Fabbro</mail>
-</author>
-
-<abstract>
-  This guide explains the use of linear algebra libraries and focus on
-  how to use the different implementations of BLAS and LAPACK available on Gentoo.
-</abstract>
-
-<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<license/>
-
-<version>1.0</version>
-<date>2010-12-22</date>
-
-<chapter>
-<title>Introduction</title>
-<section>
-<body>
-
-<p>
-  There are <uri link="http://en.wikipedia.org/wiki/List_of_numerical_libraries">many</uri>
-  performant numerical libraries available. 
-  The Basic Linear Algebra Subprograms (BLAS) and the Linear Algebra PACKage (LAPACK)
-  are well designed linear algebra libraries developed by the
-  High Performance Computing (HPC) community. BLAS is an API of dense
-  matrix and vectors products, while LAPACK provides routines for
-  solving systems of linear equations. Both are widely used in
-  many scientific applications and it is, therefore, important to 
-  have efficient implementations available.
-</p>
-
-<p>
-  BLAS and LAPACK were originally written in FORTRAN 77. Since then, a
-  number of additional language wrappers have been developed for
-  languages like C, C++, FORTRAN 95, Java, Python, etc...
-  Netlib offers exact implementations of the APIs and they are called
-  "reference" libraries.
-</p>
-
-<ul>
-<li>
-  <uri link="http://www.netlib.org/blas/">BLAS</uri>: FORTRAN 77 and C
-  (CBLAS) implementations of BLAS
-</li>
-<li>
-  <uri link="http://www.netlib.org/lapack/">LAPACK</uri>: FORTRAN 77 and
-  C (LAPACKE) implementations of LAPACK
-</li>
-</ul>
-
-<p>
-  
-</p>
-
-<ul>
-<li>
-  <uri link="http://www.netlib.org/blacs/">BLACS</uri>: FORTRAN 77 and C
-  implementations of BLACS
-</li>
-<li>
-  <uri link="http://www.netlib.org/scalapack/">ScaLAPACK</uri>: FORTRAN 77 and
-  C implementations of PBLAS and ScaLAPACK
-</li>
-</ul>
-
-<p>
-  In addition, Gentoo provides a number of optimized implementations
-  of the above linear algebra libraries that will be described
-  below. You can switch between implementations with the
-  Gentoo's <c>eselect</c> system and the widely used <c>pkg-config</c>
-  tool.
-</p>
-
-<p>
-  It is important to note that if you require, e.g., a well performing 
-  BLAS implementation, simply emerging X over Y often is not enough. Rather, you will have
-  to carefully benchmark your applications since performance may depend 
-  on many factors,
-  such as hardware or network.
-  If you are simply looking for a well performing and well tested
-  implementation, the reference ebuilds will likely be your best choice.
-</p>
-
-
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>For Users</title>
-<section>
-<title>Installing</title>
-<body>
-
-<p>
-  If best possible performance is not of paramount importance for you 
-  and you simply need BLAS and/or LAPACK, just emerge the virtual
-  package:
-</p>
-
-<pre caption="Installing">
-# <i>emerge lapack</i>
-</pre>
-
-<p>
-  This will install both <><> and <><> the reference packages from
-  <uri>http://www.netlib.org/</uri> . They are well tested, easy to debug
-  implementations. They should satisfy most users; if they're all you need, you're
-  done reading.
-</p>
-
-<p>
-However, if:
-</p>
-
-<ul>
-  <li>linear algebra libraries are critical for the speed of your applications</li>
-  <li>you absolutely need to build the fastest computer</li>
-  <li>you want to help Gentoo sci project to improve their packages</li>
-</ul>
-
-<p>
-... then read on, and be sure to file bugs both to Gentoo and upstream.
-</p>
-
-<p>
-  There is a number of optimized implementations of these libraries in the Portage
-  tree:
-</p>
-
-<ul>
-  <li>
-   <uri link="http://math-atlas.sourceforge.net">ATLAS</uri>: Automatically
-   Tuned Linear Algebra Software is an open-source package that empirically
-   tunes the library to the machine it is being compiled on. It provides BLAS
-   (FORTRAN 77 and C), and LAPACK implementations on various architectures.
-  </li>
-  <li>
-   <uri
-   link="http://www.tacc.utexas.edu/tacc-projects/gotoblas2/">GotoBLAS</uri>:
-   Goto BLAS provides open-source, free for academic use, hand-coded
-   machine language, processor optimized versions of the FORTRAN 77
-   and C BLAS routines. Still claims to be the fastest BLAS.
-  </li>
-  <li>
-    <uri link="http://software.intel.com/en-us/articles/intel-mkl/">MKL</uri>:
-    Intel® Math Kernel Library is a closed-source but free package for
-    non-commercial use on Linux systems containing implementations of all the linear
-    algebra libraries mentioned here.
-  </li>
-</ul>
-
-<p>
-  Usually performance gain is noticeable mainly with BLAS, since LAPACK routines
-  depend on BLAS kernels.
-</p>
-
-</body>
-</section>
-
-
-<section>
-<title>Developping with the installed linear algebra libraries</title>
-<body>
-
-<p>
-  We took great care to make sure that each package provides
-  consistent pkg-config files generated by us.
-  Compiling and linking becomes straightforward:
-</p>
-
-<pre caption="Compiling and linking linear algebra libraries">
-# <i>pkg-config --libs blas</i>    <comment>(To link with FORTRAN 77 BLAS library)</comment>
-# <i>pkg-config --cflags cblas</i> <comment>(To compile against C BLAS library)</comment>
-# <i>pkg-config --libs cblas</i>   <comment>(To link with C BLAS library)</comment>
-# <i>pkg-config --libs scalapack</i>  <comment>(To link with the ScaLAPACK library)</comment>
-</pre>
-
-<p>
-  <c>pkg-config</c> files are available for all implementations and
-  various alternatives within implementations. The default names of
-  the implementations are: blas, cblas, lapack, lapacke, blacs and
-  scalapack, and they can be chosen with <c>eselect</c>. You can also always compile or link
-  with an library not selected for the 
-  More information on using <c>pkg-config</c> can be obtained with <c>man pkg-config</c>. 
-</p>
-
-</body>
-</section>
-<section>
-<title>Selecting libraries</title>
-<body>
-
-<p>
-  You can switch BLAS, CBLAS and LAPACK implementations with
-  <c>eselect</c>. you can view which implementations of CBLAS
-  are available.
-</p>
-
-<pre caption="Viewing available implementations of CBLAS">
-# <i>eselect cblas list</i>
-Installed CBLAS for library directory lib64
-[1]   atlas
-[2]   atlas-threads
-[3]   gsl
-[4]   mkl-threads *
-[5]   reference
-</pre>
-
-<p>
-  The implementation marked with an asterisk (*) is the currently
-  selected implementation. To switch implementations, run:
-</p>
-
-<pre caption="Switching to the threaded ATLAS implementation of BLAS">
-# <i>eselect blas set atlas-threads</i>
-</pre>
-
-<p>
-  To learn more about the <c>eselect</c> tool, visit the 
-  <uri link="http://www.gentoo.org/proj/en/eselect/user-guide.xml">eselect guide</uri>
-</p>
-
-<p>
-  When selecting your linear algebra profiles try to avoid mixing
-  different implementations since we don't have any mechanism to enforce
-  reasonable profiles. However, here is a list of well performing
-  profile combinations that have been used successfully in the past:
-</p>
-<ul>
-  <li> performant on most CPUs:
-    <ul>
-      <li>blas, cblas: atlas (or atlas-threads with multi-processor)</li>
-      <li>lapack, lapacke: atlas</li>
-    </ul>
-  </li>
-  <li> performant on most CPUs:
-    <ul>
-      <li>blas, cblas: goto2 </li>
-      <li>lapack, lapacke: reference</li>
-    </ul>
-  </li>
-  <li> performant on AMD based CPUs:
-    <ul>
-      <li>cblas: reference</li>
-    </ul>
-  </li>
-  <li> performant on Intel based CPUs:
-    <ul>
-      <li>blas,cblas,lapack: mkl-threads</li>
-    </ul>
-  </li>
-</ul>
-
-</body>
-</section>
-
-<section>
-<title>Choosing a compiler</title>
-<body>
-
-<p>
-  All the above libraries have been tested with the GNU compiler
-  collections (gcc, gfortran).
-  There are many available C compilers and a few FORTRAN (ifort,
-  Open64) compilers on Gentoo and many other FORTRAN compilers outside
-  of Gentoo ().
-</p>
-
-<pre caption="Installing BLAS with the Intel FORTRAN compiler">
-# <i>F77=ifort FFLAGS="-O2 -mp1" emerge blas-reference</i>
-</pre>
-
-<p>
-  Depending on your hardware, a small performance gain can be noticed thanks to
-  vectorization. The <c>-mp</c> flag maintains floating-point precision, since by
-  default ifort is pretty aggressive on floating point arithmetic, and we are
-  actually compiling a math package. Try <c>man ifort</c> to see additional flags
-  to fit your hardware.
-</p>
-
-<p>
-  Some of the implementations let you specify the Intel® C compiler as
-  well. Please beware that not all libraries compile with all
-  combinations.  You should receive an error during the emerge in case you have
-  chosen an incompatible combination.
-</p>
-
-<p>
-  As usual for Gentoo, there are many combinations of USE flags and
-  compilers with which you could compile a package. Unfortunately
-  switching compilers between BLAS and LAPACK might not be always
-  compatible. For example: 
-</p>
-
-<pre caption="Looking for trouble combinations">
-# <i>FC=gfortran FFLAGS="-O2" emerge lapack-reference</i>
-</pre>
-
-<p>
-  This will most likely break things or not even compile.
-</p>
-
-<p>
-  Try to be consistent in your choice. Stay with the GCC most of the time will
-  avoid you some trouble, unless you want to use the MKL, in which case the Intel
-  compilers make a good combination.
-</p>
-
-</body>
-</section>
-<section>
-<title>Documentation</title>
-<body>
-
-<p>
-  If you need BLAS or LAPACK to develop your own programs, the documentation
-  becomes pretty handy. Setting the USE="doc" flag for the corresponding BLAS or
-  LAPACK package will install man pages and quick reference sheets from the
-  <c>app-doc/blas-docs</c> and <c>app-doc/lapack-docs</c> packages. They are
-  standard and valid for all implementations. For optimized packages, the
-  USE="doc" flags will usually install extra doc in PDF or HTML format.
-</p>
-
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>For ebuild developers</title>
-<section>
-
-<section>
-<title>Packages with BLAS/LAPACK dependencies</title>
-<body>
-
-<p>
-  You need two things:
-  set [R]DEPEND to <c>virtual/<imp></c>. To build some
-  packages, you m need to use the pkg-config tool. If you are lucky, the
-  package uses autotools together with the autoconf <>AX_BLAS and <>AX_LAPACK M4
-  macros. In this case, the configuration step becomes simple. For example:
-</p>
-
-<pre caption="Sample package configuration with autotools">
-<keyword>econf</keyword> --with-blas="<var>$(pkg-config --libs blas)</var>"
-</pre>
-
-</body>
-</section>
-
-
-
-<title>Providing new implementations</title>
-<body>
-
-<p>
-  The Portage tree contains many ebuilds that depend on the
-  BLAS/CBLAS/LAPACK/BLACS/ScaLAPACK libraries. As there is more than
-  one possible implementation, the Gentoo Science Project
-  reorganized all the packages to provide <c>virtual</c>. All ebuilds using
-  should depend on this virtual package, unless it is explicitly
-  known to break with a specific implementation.
-</p>
-
-<p>
-  To work with Gentoo's configuration tools
-  <c>app-admin/eselect-{blas,cblas,lapack}</c>, and the virtual, every ebuild that
-  installs a BLAS implementation must fulfill following requirements:
-</p>
-
-<ol>
-<li>
-  The ebuild must install an eselect file for each profile it provides. The
-  libraries should link to the ones in <path>/usr/$(get_libdir)</path>
-  directories and the include files in <path>/usr/include</path>:
- <ul>
-      <li>
-	<path>libblas.so[.0]</path> - Shared object for FORTRAN BLAS
-	applications
-      </li>
-      <li>
-        <path>libblas.a</path> - Static library for FORTRAN BLAS applications
-      </li>
-      <li>
-        <path>libcblas.so[.0]</path> - Shared object for C/C++ CBLAS applications
-      </li>
-      <li>
-        <path>libcblas.a</path> - Static library for C/C++ CBLAS applications
-      </li>
-      <li><path>cblas.h</path> - Include header for C/C++ applications</li>
-      <li>
-        <path>liblapack.so[.0]</path> - Shared object for FORTRAN LAPACK
-	applications
-      </li>
-      <li>
-        <path>liblapack.a</path> - Static library for FORTRAN LAPACK applications
-      </li>
-    </ul>
-  </li>
-  <li>
-    The ebuild must install a <path>blas.pc</path>, <path>cblas.pc</path> and/or
-    <path>lapack.pc</path> pkg-config file and therefore RDEPEND on
-    <c>dev-util/pkgconfig</c>.  They should also be included in the eselect
-    files, and link to the <path>/usr/$(get_libdir)/pkgconfig</path> directory:
-    <ul>
-      <li><path>blas.pc</path> - BLAS pkg-config file</li>
-      <li><path>cblas.pc</path> - CBLAS pkg-config file</li>
-      <li><path>lapack.pc</path> - LAPACK pkg-config file</li>
-    </ul>
-  </li>
-  <li>Be included in the virtual package as a possible provider:
-    <ul>
-      <li><c>virtual/blas</c> - BLAS virtual package</li>
-      <li><c>virtual/cblas</c> - CBLAS virtual package</li>
-      <li><c>virtual/lapack</c> - LAPACK virtual package</li>
-    </ul>
-  </li>
-</ol>
- 
-<p>
-  The easiest way of understanding all this is probably getting inspiration from
-  one of the available packages. Currently the Portage tree provide the following
-  virtual packages:
-</p>
-
-<table>
-<tr>
-  <th>Package name</th>
-  <th>virtual/blas</th>
-  <th>virtual/cblas</th>
-  <th>virtual/lapack</th>
-  <th>virtual/lapacke</th>
-  <th>virtual/blacs</th>
-  <th>virtual/scalapack</th>
-</tr>
-<tr>
-  <ti><c>sci-libs/atlas</c></ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/gotoblas2</c></ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/blas-reference</c></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/cblas-reference</c></ti>
-  <ti></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/gsl</c></ti>
-  <ti></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/lapack-reference</c></ti>
-  <ti></ti>
-  <ti></ti>
-  <ti>*</ti>
-  <ti></ti>
-  <ti></ti>
-  <ti></ti>
-</tr>
-<tr>
-  <ti><c>sci-libs/mkl</c></ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-  <ti>*</ti>
-</tr>
-</table>
-
-</body>
-</section>
-
-</chapter>
-
-<chapter>
-<title>Benchmarks</title>
-<section>
-<body>
-
-<p>
-  If you feel inclined to write an ebuild for these, you
-  are more than welcomed to file it on our <uri
-  link="http://bugs.gentoo.org">Bugzilla</uri>.
-</p>
-
-</body>
-</section>
-</chapter>
-
-</guide>
--- a/profiles/package.mask
+++ b/profiles/package.mask
@ -42,7 +42,3 @@ sci-biology/samri
 =sci-biology/afni-19.0.21
 =sci-biology/afni-18.1.04

-# Sebastien Fabbro <bicatali@gentoo.org> (23 Aug 2011)
-# mask old blas from main tree to allow smoother transition to
-# new blas/lapack framework
-=sci-libs/blas-reference-20070226*
--- a/sci-libs/blas-reference/Manifest
+++ b/sci-libs/blas-reference/Manifest
@ -1,2 +0,0 @@
-DIST lapack-3.7.0.tgz 7359812 BLAKE2B 20aa42e22d8c920d1360afe41ceec7b36f6cd5fbe43ca9d7848ef7cc45a64a0314cb1321941c1a7c03654f41e28ec805445882ded0ca0ea07674e70b66cba6b5 SHA512 e4f4c7d0ba8a096eeb813160c6dbcdd535647df6b2ad5beac9181908158956b31d1a9554ec9b9836fd44fe7404c1f377b297cbb20d744f20d70e357fd246c91b
-DIST lapack-3.8.0.tar.gz 7426094 BLAKE2B 27cd75eea498250382b2df6f5d7dc95fdee8d37b1a0faba5296ca0145ec40a1165a4ecc727aa1647086be6783b50cf475f79cea0f30f541da789051db99b2f37 SHA512 17786cb7306fccdc9b4a242de7f64fc261ebe6a10b6ec55f519deb4cb673cb137e8742aa5698fd2dc52f1cd56d3bd116af3f593a01dcf6770c4dcc86c50b2a7f
--- a/sci-libs/blas-reference/blas-reference-20161223-r100.ebuild
+++ b/sci-libs/blas-reference/blas-reference-20161223-r100.ebuild
@ -1,110 +0,0 @@
-# Copyright 1999-2017 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-PYTHON_COMPAT=( python2_7 )
-
-NUMERIC_MODULE_NAME="refblas"
-
-inherit alternatives-2 cmake-utils eutils fortran-2 numeric-int64-multibuild python-any-r1 toolchain-funcs
-
-LPN=lapack
-LPV=3.7.0
-
-DESCRIPTION="Reference implementation of BLAS"
-HOMEPAGE="http://www.netlib.org/lapack/"
-SRC_URI="http://www.netlib.org/${LPN}/${LPN}-${LPV}.tgz"
-
-LICENSE="BSD"
-SLOT="0/${LPV}"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
-IUSE="static-libs test"
-
-REQUIRED_USE="test? ( ${PYTHON_REQUIRED_USE} )"
-
-RDEPEND=""
-DEPEND="${RDEPEND}
-	test? ( ${PYTHON_DEPS} )
-	virtual/pkgconfig"
-
-S="${WORKDIR}/${LPN}-${LPV}"
-PATCHES=( "${FILESDIR}/lapack-reference-${LPV}-fix-build-system.patch" )
-
-src_prepare() {
-	default
-
-	# rename library to avoid collision with other blas implementations
-	# ${LIBNAME} and ${PROFNAME} are not defined here, they are in single
-	# quotes in the following seds.  They are later set by defining cmake
-	# variables with -DPROFNAME etc in src_configure
-	sed -i \
-		-e 's:\([^xc]\)blas:\1${LIBNAME}:g' \
-		-e '/PROPERTIES/s:blas:${LIBNAME}:g' \
-		CMakeLists.txt \
-		BLAS/SRC/CMakeLists.txt || die
-	sed -i \
-		-e '/Name: /s:blas:@PROFNAME@:' \
-		-e 's:-lblas:-l@LIBNAME@:g' \
-		 BLAS/blas.pc.in || die
-	sed -i \
-		-e 's:blas):${LIBNAME}):' \
-		BLAS/TESTING/CMakeLists.txt || die
-	sed -i \
-		-e 's:BINARY_DIR}/blas:BINARY_DIR}/${PROFNAME}:' \
-		BLAS/CMakeLists.txt || die
-}
-
-src_configure() {
-	blas_configure() {
-		local FCFLAGS="${FCFLAGS}"
-		append-fflags $($(tc-getPKG_CONFIG) --cflags ${blas_profname})
-		append-fflags $(get_abi_CFLAGS)
-		append-fflags $(numeric-int64_get_fortran_int64_abi_fflags)
-
-		local profname=$(numeric-int64_get_module_name)
-		local libname="${profname//-/_}"
-
-		local mycmakeargs=(
-			-Wno-dev
-			-DPROFNAME="${profname}"
-			-DLIBNAME="${libname}"
-			-DUSE_OPTIMIZED_BLAS=OFF
-			-DCMAKE_Fortran_FLAGS="${FCFLAGS}"
-			-DLAPACK_PKGCONFIG_FFLAGS="$(numeric-int64_get_fortran_int64_abi_fflags)"
-			-DBUILD_TESTING="$(usex test)"
-		)
-		if $(numeric-int64_is_static_build); then
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=OFF
-				-DBUILD_STATIC_LIBS=ON
-			)
-		else
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=ON
-				-DBUILD_STATIC_LIBS=OFF
-			)
-		fi
-		cmake-utils_src_configure
-	}
-	numeric-int64-multibuild_foreach_all_abi_variants blas_configure
-}
-
-src_compile() {
-	local each target_dirs=( BLAS )
-	use test && target_dirs+=( TESTING )
-	for each in ${target_dirs[@]}; do
-		numeric-int64-multibuild_foreach_all_abi_variants \
-			cmake-utils_src_compile -C ${each}
-	done
-
-}
-
-src_test() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_test
-}
-
-src_install() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_install -C BLAS
-	numeric-int64-multibuild_install_alternative blas reference
-}
--- a/sci-libs/blas-reference/blas-reference-20171112-r100.ebuild
+++ b/sci-libs/blas-reference/blas-reference-20171112-r100.ebuild
@ -1,109 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-PYTHON_COMPAT=( python2_7 )
-
-NUMERIC_MODULE_NAME="refblas"
-
-inherit alternatives-2 cmake-utils eutils fortran-2 numeric-int64-multibuild python-any-r1 toolchain-funcs
-
-LPN=lapack
-LPV=3.8.0
-
-DESCRIPTION="Reference implementation of BLAS"
-HOMEPAGE="http://www.netlib.org/lapack/"
-SRC_URI="http://www.netlib.org/${LPN}/${LPN}-${LPV}.tar.gz"
-
-LICENSE="BSD"
-SLOT="0/${LPV}"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
-IUSE="static-libs test"
-
-REQUIRED_USE="test? ( ${PYTHON_REQUIRED_USE} )"
-
-RDEPEND=""
-DEPEND="${RDEPEND}
-	test? ( ${PYTHON_DEPS} )
-	virtual/pkgconfig"
-
-S="${WORKDIR}/${LPN}-${LPV}"
-
-src_prepare() {
-	cmake-utils_src_prepare
-
-	# rename library to avoid collision with other blas implementations
-	# ${LIBNAME} and ${PROFNAME} are not defined here, they are in single
-	# quotes in the following seds.  They are later set by defining cmake
-	# variables with -DPROFNAME etc in src_configure
-	sed -i \
-		-e 's:\([^xc]\)blas:\1${LIBNAME}:g' \
-		-e '/PROPERTIES/s:blas:${LIBNAME}:g' \
-		CMakeLists.txt \
-		BLAS/SRC/CMakeLists.txt || die
-	sed -i \
-		-e '/Name: /s:blas:@PROFNAME@:' \
-		-e 's:-lblas:-l@LIBNAME@:g' \
-		 BLAS/blas.pc.in || die
-	sed -i \
-		-e 's:blas):${LIBNAME}):' \
-		BLAS/TESTING/CMakeLists.txt || die
-	sed -i \
-		-e 's:BINARY_DIR}/blas:BINARY_DIR}/${PROFNAME}:' \
-		BLAS/CMakeLists.txt || die
-}
-
-src_configure() {
-	blas_configure() {
-		local FCFLAGS="${FCFLAGS}"
-		append-fflags $($(tc-getPKG_CONFIG) --cflags ${blas_profname})
-		append-fflags $(get_abi_CFLAGS)
-		append-fflags $(numeric-int64_get_fortran_int64_abi_fflags)
-
-		local profname=$(numeric-int64_get_module_name)
-		local libname="${profname//-/_}"
-
-		local mycmakeargs=(
-			-Wno-dev
-			-DPROFNAME="${profname}"
-			-DLIBNAME="${libname}"
-			-DUSE_OPTIMIZED_BLAS=OFF
-			-DCMAKE_Fortran_FLAGS="${FCFLAGS}"
-			-DLAPACK_PKGCONFIG_FFLAGS="$(numeric-int64_get_fortran_int64_abi_fflags)"
-			-DBUILD_TESTING="$(usex test)"
-		)
-		if $(numeric-int64_is_static_build); then
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=OFF
-				-DBUILD_STATIC_LIBS=ON
-			)
-		else
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=ON
-				-DBUILD_STATIC_LIBS=OFF
-			)
-		fi
-		cmake-utils_src_configure
-	}
-	numeric-int64-multibuild_foreach_all_abi_variants blas_configure
-}
-
-src_compile() {
-	local each target_dirs=( BLAS )
-	use test && target_dirs+=( TESTING )
-	for each in ${target_dirs[@]}; do
-		numeric-int64-multibuild_foreach_all_abi_variants \
-			cmake-utils_src_compile -C ${each}
-	done
-
-}
-
-src_test() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_test
-}
-
-src_install() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_install -C BLAS
-	numeric-int64-multibuild_install_alternative blas reference
-}
--- a/sci-libs/blas-reference/blas-reference-99999999.ebuild
+++ b/sci-libs/blas-reference/blas-reference-99999999.ebuild
@ -1,108 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-PYTHON_COMPAT=( python2_7 )
-
-NUMERIC_MODULE_NAME="refblas"
-
-inherit alternatives-2 cmake-utils fortran-2 numeric-int64-multibuild python-any-r1 toolchain-funcs subversion
-
-LPN=lapack
-LPV=3.8.0
-
-DESCRIPTION="Reference implementation of BLAS"
-HOMEPAGE="http://www.netlib.org/lapack/"
-ESVN_REPO_URI="https://icl.cs.utk.edu/svn/lapack-dev/${LPN}/trunk"
-
-LICENSE="BSD"
-SLOT="0/${LPV}"
-KEYWORDS=""
-IUSE="static-libs test"
-
-REQUIRED_USE="test? ( ${PYTHON_REQUIRED_USE} )"
-
-RDEPEND=""
-DEPEND="${RDEPEND}
-	test? ( ${PYTHON_DEPS} )
-	virtual/pkgconfig"
-
-S="${WORKDIR}/${LPN}-${LPV}"
-
-src_prepare() {
-	cmake-utils_src_prepare
-	# rename library to avoid collision with other blas implementations
-	# ${LIBNAME} and ${PROFNAME} are not defined here, they are in single
-	# quotes in the following seds.  They are later set by defining cmake
-	# variables with -DPROFNAME etc in src_configure
-	sed -i \
-		-e 's:\([^xc]\)blas:\1${LIBNAME}:g' \
-		-e '/PROPERTIES/s:blas:${LIBNAME}:g' \
-		CMakeLists.txt \
-		BLAS/SRC/CMakeLists.txt || die
-	sed -i \
-		-e '/Name: /s:blas:${PROFNAME}:' \
-		-e 's:-lblas:-l${LIBNAME}:g' \
-		 BLAS/blas.pc.in || die
-	sed -i \
-		-e 's:blas):${LIBNAME}):' \
-		BLAS/TESTING/CMakeLists.txt || die
-	sed -i \
-		-e 's:BINARY_DIR}/blas:BINARY_DIR}/${PROFNAME}:' \
-		BLAS/CMakeLists.txt || die
-}
-
-src_configure() {
-	blas_configure() {
-		local FCFLAGS="${FCFLAGS}"
-		append-fflags $($(tc-getPKG_CONFIG) --cflags ${blas_profname})
-		append-fflags $(get_abi_CFLAGS)
-		append-fflags $(numeric-int64_get_fortran_int64_abi_fflags)
-
-		local profname=$(numeric-int64_get_module_name)
-		local libname="${profname//-/_}"
-
-		local mycmakeargs=(
-			-Wno-dev
-			-DPROFNAME="${profname}"
-			-DLIBNAME="${libname}"
-			-DUSE_OPTIMIZED_BLAS=OFF
-			-DCMAKE_Fortran_FLAGS="${FCFLAGS}"
-			-DLAPACK_PKGCONFIG_FFLAGS="$(numeric-int64_get_fortran_int64_abi_fflags)"
-			$(cmake-utils_use_build test TESTING)
-		)
-		if $(numeric-int64_is_static_build); then
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=OFF
-				-DBUILD_STATIC_LIBS=ON
-			)
-		else
-			mycmakeargs+=(
-				-DBUILD_SHARED_LIBS=ON
-				-DBUILD_STATIC_LIBS=OFF
-			)
-		fi
-		cmake-utils_src_configure
-	}
-	numeric-int64-multibuild_foreach_all_abi_variants blas_configure
-}
-
-src_compile() {
-	local each target_dirs=( BLAS )
-	use test && target_dirs+=( TESTING )
-	for each in ${target_dirs[@]}; do
-		numeric-int64-multibuild_foreach_all_abi_variants \
-			cmake-utils_src_compile -C ${each}
-	done
-
-}
-
-src_test() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_test
-}
-
-src_install() {
-	numeric-int64-multibuild_foreach_all_abi_variants cmake-utils_src_install -C BLAS
-	numeric-int64-multibuild_install_alternative blas reference
-}
--- a/sci-libs/blas-reference/files/lapack-fix-build-system.patch
+++ b/sci-libs/blas-reference/files/lapack-fix-build-system.patch
@ -1,92 +0,0 @@
--- lapack-3.6.0/BLAS/blas.pc.in
-+++ lapack-3.6.0/BLAS/blas.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
- 
- Name: blas
- Description: Basic Linear Algebra Subprograms F77 reference implementations
--- lapack-3.6.0/BLAS/CMakeLists.txt
-+++ lapack-3.6.0/BLAS/CMakeLists.txt
-@@ -2,7 +2,7 @@
- if(BUILD_TESTING)
- add_subdirectory(TESTING)
- endif(BUILD_TESTING)
-configure_file(${CMAKE_CURRENT_SOURCE_DIR}/blas.pc.in ${CMAKE_CURRENT_BINARY_DIR}/blas.pc)
-+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/blas.pc.in ${CMAKE_CURRENT_BINARY_DIR}/blas.pc @ONLY)
- install(FILES
-   ${CMAKE_CURRENT_BINARY_DIR}/blas.pc
-   DESTINATION ${PKG_CONFIG_DIR}
--- lapack-3.6.0/CBLAS/cblas.pc.in
-+++ lapack-3.6.0/CBLAS/cblas.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
- 
- Name: lapacke
- Description: C Standard Interface to BLAS Linear Algebra PACKage
--- lapack-3.6.0/CBLAS/CMakeLists.txt
-+++ lapack-3.6.0/CBLAS/CMakeLists.txt
-@@ -71,7 +71,7 @@
-   ${LAPACK_BINARY_DIR}/cblas-config.cmake @ONLY)
- 
- 
-configure_file(${CMAKE_CURRENT_SOURCE_DIR}/cblas.pc.in ${CMAKE_CURRENT_BINARY_DIR}/cblas.pc)
-+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/cblas.pc.in ${CMAKE_CURRENT_BINARY_DIR}/cblas.pc @ONLY)
-   install(FILES
-   ${CMAKE_CURRENT_BINARY_DIR}/cblas.pc
-   DESTINATION ${PKG_CONFIG_DIR}
--- lapack-3.6.0/CMakeLists.txt
-+++ lapack-3.6.0/CMakeLists.txt
-@@ -333,7 +333,7 @@
-   ${LAPACK_BINARY_DIR}/lapack-config.cmake @ONLY)
- 
- 
-configure_file(${CMAKE_CURRENT_SOURCE_DIR}/lapack.pc.in ${CMAKE_CURRENT_BINARY_DIR}/lapack.pc)
-+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/lapack.pc.in ${CMAKE_CURRENT_BINARY_DIR}/lapack.pc @ONLY)
-   install(FILES
-   ${CMAKE_CURRENT_BINARY_DIR}/lapack.pc
-   DESTINATION ${PKG_CONFIG_DIR}
--- lapack-3.6.0/LAPACKE/CMakeLists.txt
-+++ lapack-3.6.0/LAPACKE/CMakeLists.txt
-@@ -65,7 +65,7 @@
- endif(BUILD_TESTING)
- 
- 
-configure_file(${CMAKE_CURRENT_SOURCE_DIR}/lapacke.pc.in ${CMAKE_CURRENT_BINARY_DIR}/lapacke.pc)
-+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/lapacke.pc.in ${CMAKE_CURRENT_BINARY_DIR}/lapacke.pc @ONLY)
-  install(FILES
-   ${CMAKE_CURRENT_BINARY_DIR}/lapacke.pc
-   DESTINATION ${PKG_CONFIG_DIR}
--- lapack-3.6.0/LAPACKE/lapacke.pc.in
-+++ lapack-3.6.0/LAPACKE/lapacke.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
- 
- Name: lapacke
- Description: C Standard Interface to LAPACK Linear Algebra PACKage
--- lapack-3.6.0/lapack.pc.in
-+++ lapack-3.6.0/lapack.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
- 
- Name: lapack
- Description: FORTRAN reference implementation of LAPACK Linear Algebra PACKage
--- a/sci-libs/blas-reference/files/lapack-reference-3.7.0-fix-build-system.patch
+++ b/sci-libs/blas-reference/files/lapack-reference-3.7.0-fix-build-system.patch
@ -1,56 +0,0 @@
-diff --git a/BLAS/blas.pc.in b/BLAS/blas.pc.in
-index 7fd6f1e..e52f3ad 100644
--- a/BLAS/blas.pc.in
-+++ b/BLAS/blas.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
- 
- Name: BLAS
- Description: FORTRAN reference implementation of BLAS Basic Linear Algebra Subprograms
-diff --git a/CBLAS/cblas.pc.in b/CBLAS/cblas.pc.in
-index 4a938fe..311aed9 100644
--- a/CBLAS/cblas.pc.in
-+++ b/CBLAS/cblas.pc.in
-@@ -1,5 +1,7 @@
-prefix=@prefix@
-libdir=@libdir@
-+prefix=@CMAKE_INSTALL_PREFIX@
-+exec_prefix=${prefix}
-+libdir=${exec_prefix}/@CMAKE_INSTALL_LIBDIR@
-+includedir=${prefix}/include
-