[MacPorts] #64379: lapack @3.10.0: cmake files in wrong location
MacPorts
noreply at macports.org
Mon Mar 18 09:27:57 UTC 2024
#64379: lapack @3.10.0: cmake files in wrong location
------------------------+----------------------
Reporter: lepus2589 | Owner: (none)
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 2.7.1
Resolution: | Keywords: haspatch
Port: lapack |
------------------------+----------------------
Comment (by lepus2589):
For me, the Homebrew installation works. The files are sym-linked into
{{{/opt/homebrew/opt/lapack}}}. Also, if you try to discover {{{lapacke}}}
in your {{{CMakeLists.txt}}}, use the {{{lapacke_DIR}}} CMake variable,
not {{{LAPACK_DIR}}}.
With my example {{{CMakeLists.txt}}} from above and the following command
line, the Homebrew lapack install works:
{{{
$ cmake -B ./build -D
"lapacke_DIR=/opt/homebrew/opt/lapack/lib/cmake/lapacke-3.12.0" .
-- The C compiler identification is Clang 17.0.6
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/local/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done (1.3s)
-- Generating done (0.0s)
-- Build files have been written to: ./build
}}}
CMake succeeds without further comment. In my
{{{./build/CMakeCache.txt}}}, I have the line
{{{lapacke_DIR:UNINITIALIZED=/opt/homebrew/opt/lapack/lib/cmake/lapacke-3.12.0}}}.
I can even use the more general form
{{{
$ cmake -B ./build -D "CMAKE_PREFIX_PATH=/opt/homebrew/opt/lapack" .
}}}
So, I still have to help CMake discover the initial config file, but the
config files are consistent and can discover each other automatically.
--
Ticket URL: <https://trac.macports.org/ticket/64379#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list