From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: KataGo-1.11.0
Date: Sat, 30 Jul 2022 03:41:35 +0200 [thread overview]
Message-ID: <20220730014135.TRY4IMw2ILEucCQ-PM0UASpQKa2ZnMH_su67X7KquE0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38190@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
New comment by jason1987d on void-packages repository
https://github.com/void-linux/void-packages/pull/38190#issuecomment-1200061488
Comment:
For Eigen (CPU based) specifically, I found this error.
```
CMake Error at CMakeLists.txt:296 (find_package):
By not providing "FindEigen3.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Eigen3", but
CMake did not find one.
Could not find a package configuration file provided by "Eigen3" with any
of the following names:
Eigen3Config.cmake
eigen3-config.cmake
Add the installation prefix of "Eigen3" to CMAKE_PREFIX_PATH or set
"Eigen3_DIR" to a directory containing one of the above files. If "Eigen3"
provides a separate development package or SDK, be sure it has been
installed.
```
I see 'eigen' itself listed in void repos, but not eigen-devel like how the KataGo docs mention libeigen3-dev for apt based distros. Maybe I need to edit the eigen template to add that -devel subpackage?
next prev parent reply other threads:[~2022-07-30 1:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 13:40 [PR PATCH] " jason1987d
2022-07-22 15:47 ` [PR REVIEW] " Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 17:26 ` [PR PATCH] [Updated] " jason1987d
2022-07-22 17:26 ` jason1987d
2022-07-22 18:19 ` jason1987d
2022-07-22 20:19 ` Chocimier
2022-07-22 21:24 ` jason1987d
2022-07-22 21:24 ` jason1987d
2022-07-22 21:52 ` jason1987d
2022-07-22 22:04 ` jason1987d
2022-07-22 22:09 ` [PR PATCH] [Updated] " jason1987d
2022-07-23 13:47 ` jason1987d
2022-07-23 13:48 ` jason1987d
2022-07-23 16:43 ` jason1987d
2022-07-23 16:49 ` jason1987d
2022-07-24 1:47 ` jason1987d
2022-07-25 16:34 ` [PR REVIEW] " Chocimier
2022-07-25 16:34 ` Chocimier
2022-07-26 13:33 ` [PR PATCH] [Updated] " jason1987d
2022-07-26 13:36 ` jason1987d
2022-07-26 15:19 ` [PR PATCH] [Updated] " jason1987d
2022-07-27 18:56 ` Chocimier
2022-07-29 21:16 ` [PR PATCH] [Updated] " jason1987d
2022-07-29 21:17 ` jason1987d
2022-07-29 21:18 ` jason1987d
2022-07-29 21:30 ` jason1987d
2022-07-30 1:29 ` jason1987d
2022-07-30 1:40 ` jason1987d
2022-07-30 1:40 ` jason1987d
2022-07-30 1:40 ` jason1987d
2022-07-30 1:41 ` jason1987d [this message]
2022-07-30 1:41 ` jason1987d
2022-07-30 1:45 ` jason1987d
2022-07-30 1:48 ` jason1987d
2022-07-30 13:46 ` Chocimier
2022-07-30 18:08 ` jason1987d
2022-07-30 18:19 ` [PR PATCH] [Updated] " jason1987d
2022-07-31 21:14 ` jason1987d
2022-08-02 17:57 ` [PR REVIEW] " Chocimier
2022-08-02 17:57 ` Chocimier
2022-08-02 21:15 ` jason1987d
2022-08-02 21:45 ` Chocimier
2022-08-03 4:32 ` [PR PATCH] [Updated] " jason1987d
2022-08-12 14:38 ` jason1987d
2022-09-11 5:22 ` jason1987d
2022-09-11 5:24 ` [PR PATCH] [Closed]: " jason1987d
2022-09-11 5:24 ` [PR PATCH] [Updated] " jason1987d
2022-09-11 13:53 ` jason1987d
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220730014135.TRY4IMw2ILEucCQ-PM0UASpQKa2ZnMH_su67X7KquE0@z \
--to=jason1987d@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).