(0035051)
Brad King (manager)
2014-02-07 09:21

Which distribution of LAPACK are you using and what header files do you expect to be found?

(0035052)
Philipp Möller (reporter)
2014-02-07 09:30

I would usually expect the LAPACKE headers to be found. It seems LAPACKE only became a part of the standard LAPACK distribution starting with Release 3.5.0 http://www.netlib.org/lapack/lapack-3.5.0.html [^]

I think there are two ways to handle this: provide FindLAPACKE or include the check for the include directory given the version of LAPACK is >= 3.5.0

(0035053)
Brad King (manager)
2014-02-07 09:45

The upstream reference implementation of LAPACK builds with CMake and distributes a lapack-config.cmake package configuration file. This allows CMake to find LAPACK without a FindLAPACK module. Applications can write

find_package(LAPACK NO_MODULE)

to skip the CMake-provided FindLAPACK module and simply search for lapack-config.cmake with a single LAPACK_DIR cache entry. Then that file is loaded and is responsible for providing all information.

We need to work with upstream LAPACK to provide the include directory in their lapack-config.cmake file (or perhaps a separate lapacke-config.cmake file).

(0035081)
Brad King (manager)
2014-02-10 10:45

Upstream reference lapack:

https://icl.cs.utk.edu/svn/lapack-dev/lapack/trunk [^]

revision r1472 now provides a lapacke package configuration file so one can write

find_package(LAPACKE NO_MODULE REQUIRED)
include_directories(${LAPACKE_INCLUDE_DIRS})
add_executable(myexe myexe.c)
target_link_libraries(myexe ${LAPACKE_LIBRARIES})

and work with no modifications to CMake.

(0035082)
Brad King (manager)
2014-02-10 10:49

FindLAPACK should to be taught to try to the reference lapack's package configuration file instead of looking only for the individual pieces.

Since the reference lapack is not the only implementation we may still need a FindLAPACKE that works similarly.

(0042479)
Kitware Robot (administrator)
2016-06-10 14:29

Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2014-02-06 17:08	Philipp Möller	New Issue
2014-02-07 09:21	Brad King	Note Added: 0035051
2014-02-07 09:30	Philipp Möller	Note Added: 0035052
2014-02-07 09:45	Brad King	Note Added: 0035053
2014-02-10 10:45	Brad King	Note Added: 0035081
2014-02-10 10:49	Brad King	Note Added: 0035082
2014-02-10 10:49	Brad King	Severity	minor => feature
2014-02-10 10:49	Brad King	Status	new => backlog
2014-02-10 10:49	Brad King	Summary	FindLAPACK does not export LAPACK_INCLUDE_DIR => Teach FindLAPACK to find lapack-config.cmake, maybe add FindLAPACKE
2016-06-10 14:29	Kitware Robot	Note Added: 0042479
2016-06-10 14:29	Kitware Robot	Status	backlog => resolved
2016-06-10 14:29	Kitware Robot	Resolution	open => moved
2016-06-10 14:29	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed

Notes
(0035051) Brad King (manager) 2014-02-07 09:21	Which distribution of LAPACK are you using and what header files do you expect to be found?

(0035052) Philipp Möller (reporter) 2014-02-07 09:30	I would usually expect the LAPACKE headers to be found. It seems LAPACKE only became a part of the standard LAPACK distribution starting with Release 3.5.0 http://www.netlib.org/lapack/lapack-3.5.0.html [^] I think there are two ways to handle this: provide FindLAPACKE or include the check for the include directory given the version of LAPACK is >= 3.5.0

(0035053) Brad King (manager) 2014-02-07 09:45	The upstream reference implementation of LAPACK builds with CMake and distributes a lapack-config.cmake package configuration file. This allows CMake to find LAPACK without a FindLAPACK module. Applications can write find_package(LAPACK NO_MODULE) to skip the CMake-provided FindLAPACK module and simply search for lapack-config.cmake with a single LAPACK_DIR cache entry. Then that file is loaded and is responsible for providing all information. We need to work with upstream LAPACK to provide the include directory in their lapack-config.cmake file (or perhaps a separate lapacke-config.cmake file).

(0035081) Brad King (manager) 2014-02-10 10:45	Upstream reference lapack: https://icl.cs.utk.edu/svn/lapack-dev/lapack/trunk [^] revision r1472 now provides a lapacke package configuration file so one can write find_package(LAPACKE NO_MODULE REQUIRED) include_directories(${LAPACKE_INCLUDE_DIRS}) add_executable(myexe myexe.c) target_link_libraries(myexe ${LAPACKE_LIBRARIES}) and work with no modifications to CMake.

(0035082) Brad King (manager) 2014-02-10 10:49	FindLAPACK should to be taught to try to the reference lapack's package configuration file instead of looking only for the individual pieces. Since the reference lapack is not the only implementation we may still need a FindLAPACKE that works similarly.

(0042479) Kitware Robot (administrator) 2016-06-10 14:29	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Relationships