From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [FTBFS] julia - need to specify CPU for openblas?
Date: Sun, 05 Dec 2021 04:05:04 +0100 [thread overview]
Message-ID: <20211205030504.47EwxdXm5zL8wsaihp1t-l6Zb0cWYQFKkmaOUWnqmY4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34387@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
New comment by bobertlo on void-packages repository
https://github.com/void-linux/void-packages/issues/34387#issuecomment-986157695
Comment:
It’s failing in both glibc and musl vms on a i7-10750H. It appears to be cpu detection in the auto config and threads with this error mentioned newer cpus not being detected properly yet.
iirc openblas has been updated since that pr or near then but I’m guessing it is a host info leak. I’ll try it natively when I am near that system.
next prev parent reply other threads:[~2021-12-05 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 1:05 [ISSUE] " bobertlo
2021-12-05 2:42 ` ericonr
2021-12-05 3:05 ` bobertlo [this message]
2021-12-05 6:18 ` bobertlo
2021-12-05 6:19 ` bobertlo
2022-06-18 2:13 ` github-actions
2022-06-27 20:52 ` Piraty
2022-06-27 20:52 ` Piraty
2022-07-12 2:15 ` [ISSUE] [CLOSED] " github-actions
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=20211205030504.47EwxdXm5zL8wsaihp1t-l6Zb0cWYQFKkmaOUWnqmY4@z \
--to=bobertlo@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).