[Buildroot] [PATCH 2/5] package/liblapack: add liblapack as virtual package with lapack and clapack as providers.
alexandre.payen at smile.fr
Fri Aug 9 16:03:01 UTC 2019
I realise many thinks in this lapack/clapack problem.
First of all, clapack is completly out dated ...
The last release is version 3.2.1 when lapack is at version 3.8.0
Also, since ten years, no one touch it ...
I really suggest to drop this package from buildroot ...
OpenBLAS is an implementation of BLAS. It can also generate a lapack
implementation if needed. This implementation is lapack from netlib
(lapack already present in buildroot). So, we should remove this from
OpenBLAS and use the already present lapack in the build system.
Also, lapack from netlib advise to use another BLAS implementation
than netlib BLAS. Perfect, we can use OpenBLAS implementation.
I suggest to make a virtual package libblas with OpenBLAS as provider
ATLAS could be added later. And depending from this virtual package,
a liblapack virtual package with lapack, clapack more could be added.
This is the easiest way. But be carefull because lapack generate a
libblas.so file so, just the liblapack.so should be built.
The second solution is to keep the same package architecture as now
but linking OpenBLAS and lapack. So if they are both selected,
OpenBLAS should be built with lapack, and lapack should not build
libblas.so. Else, only lapack should build normaly or only libblas.so
I think the maintain cost for the second solution is higher.
Also, it is simplier to build the first solution.
Tell me what you think of that and I will work on a patch.
Le mar. 6 août 2019 à 17:57, Alexandre PAYEN <alexandre.payen at smile.fr> a
> Hi all.
> Well, after digging lapack(with and without complex),clapack and openblas
> I got
> some new insight.
> Here is what I did :
> I gather the different libraries (lapack without complex, lapack with
> clapack and openblas) and gather from LAPACK and BLAS documentation
> function list.
> Then, for each function, I ran nm command on the library with a simple
> script. nm command can output symbols from the symtable of an ELF binary
> to -D option.
> Here is the correct line option from `man nm`
> nm -D OBJFILE
> Display the dynamic symbols rather than the normal symbols. This is only
> meaningful for dynamic objects, such as certain types of shared
> Here is the script
> nm -D $library_file > /tmp/tmp_nm
> for line in `cat $function_file` # for each line in the file
> grep -i $line /tmp/tmp_nm # check if the function is in the nm dump
> if [[ $? -ne 0 ]]
> echo $line >> $library_file.not_found # add to the not found file
> echo $line >> $library_file.found # add to the found file
> After running this script on every library with the good function set, I
> determine what is missing or not.
> I will use the function set I link to perform my analysis.
> So, first of all, clapack have complex support. This mean :
> (clapack-)libblas.so and (lapack-complex-)libblas.so have the same
> functions and
> (clapack-)liblapack.so and (lapack-complex-)liblapack.so have the same
> except one symbol which differs : `geqpfp` in not in clapack
> In theory, we could use clapack or lapack with complex support, it will
> (almost) annything.
> Openblas now,
> openblas.so and (lapack-complex-)liblapack.so have the same functions
> openblas.so and (lapack-complex-)libblas.so have the same functions.
> Theoretically, we could make two symbolic link on openblas.so named:
> - liblapack.so
> - libblas.so
> and use it as lapack and blas implementation.
> I dig deeper into openblas and I realise that openblas does not provide a
> lapack implementation. Openblas just compile lapack from netlib and link
> it to
> provide it own library openblas.lib.
> So, what about blas implementation. I'm not sure if openblas provide its
> own or
> not ...
> There is this wierd rule in openblas Makefile ...
> (cd $(NETLIB_LAPACK_DIR)/BLAS/TESTING && rm -f x* *.out)
> $(MAKE) -j 1 -C $(NETLIB_LAPACK_DIR) blas_testing
> (cd $(NETLIB_LAPACK_DIR)/BLAS/TESTING && cat *.out)
> It clearly use the test from the netlib implementation of BLAS ...
> Well ... I think, we could use those three packages as providers for
> - liblapack.so
> - libblas.so
> (by doing symlinks on Openblas).
> I still have to:
> - dig into cblas and check if openblas, lapack(complex) and clapack are
> - perform the tests with the symlinks on openblas
> - replace the files from clapack with the one from lapack.
> What do you think of this idee on virtual packages with those three
> providers ?
> Something else about Openblas. It use netlib lapack, and doing so, need a
> fortran compiler, so Thomas, you cannot use Openblas for lapack
> on your fortran-less project ...
> : http://www.netlib.org/lapack/lapacke.html#_real_functions
> : http://www.netlib.org/blas/#_blas_routines
> : https://github.com/xianyi/OpenBLAS
> Le lun. 5 août 2019 à 14:49, Alexandre PAYEN <alexandre.payen at smile.fr> a
> écrit :
>> Hi Thomas, all.
>> Le lun. 5 août 2019 à 14:27, Thomas De Schampheleire <
>> patrickdepinguin at gmail.com> a écrit :
>>> El sáb., 3 ago. 2019 a las 12:23, Arnout Vandecappelle
>>> (<arnout at mind.be>) escribió:
>>> > Hi Alex, Romain,
>>> > On 01/08/2019 23:09, Romain Naour wrote:
>>> > > lapack and clapack are both generating the same liblapack.so but
>>> does not have
>>> > > the same symbols. So the run-time is broke. They have to exclude
>>> each other.
>>> > We discussed this at the hackaton and reviewed all the options that
>>> > discussed before on the mailing list, and we concluded that the
>>> > solution is to remove clapack entirely. Everything that uses clapack
>>> > armadillo and numpy) can use lapack as well, as you mention, so the
>>> only reason
>>> > to keep clapack would be to support toolchains without Fortran
>>> compiler. Most of
>>> > our external toolchains do have Fortran support, and I expect that
>>> anybody who
>>> > cares about maths wouldn't mind enabling Fortran in their toolchains.
>>> > If anybody disagrees with that, now is the time to speak up :-)
>>> There may be cases where a toolchain is provided by a third-party,
>>> e.g. a silicon vendor like Marvell.
>>> In this case, Fortran is not necessarily provided. Depending on that
>>> third-party, it may or may not be easy to get this fixed.
>>> In our case, we have some boards with a toolchain from Marvell (no
>>> Fortran) and others where we build the toolchains ourselves. In both
>>> cases we have armadillo with clapack. Recently, we wanted to use
>>> openblas, and getting clapack to work as lapack backend for openblas
>>> did not seem to work. So for those boards were it mattered, we enabled
>>> fortran and let openblas use its own lapack implementation. For the
>>> boards with Marvell toolchain, we planned to keep the existing
>>> armadillo+clapack situation.
>>> So removing clapack altogether would not be desirable for that case.
>>> Note also that openblas also has lapack inside its sources. So it
>>> could also a provider for liblapack in the case of a virtual-package
>> Okay, good to know, I will check in this way also. I will check which
>> package use
>> libopenblas.so and how it use it.
>>> I searched but could not find extensive discussion on the mailing list
>>> regarding this topic.
>>> What is the actual problem with introducing a virtual-package?
>> So, for want I know and understand :
>> - lapack and clapack generate the same library files : liblapack.so and
>> - lapack generate libcblas.so and clapack does not.
>> - lapack can be built with complex support. It double the size of the
>> library so it
>> should add a lot of symbols. I guess clapack is already built with complex
>> support but I'm not sure ...
>> A new idee is to introduce virtual package to generate :
>> - liblapack.so
>> - libblas.so
>> - libcblas.so
>> with lapack and clapack as providers.
>> As you said Thomas, openblas has it own lapack implementation so,
>> we could add openblas as a provider and create a symbolic link to
>> I will inspect those implementations using readefl or a similar tool and
>> try to
>> assert that we can use this solution.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the buildroot