From: kwshi <kwshi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: julia: update to 1.7.1.
Date: Sat, 05 Feb 2022 08:03:36 +0100 [thread overview]
Message-ID: <20220205070336.qC0gfBs6eKUxxcOW2Q7hHi2DAEd8adPxdXyT07T5TUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35270@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
New comment by kwshi on void-packages repository
https://github.com/void-linux/void-packages/pull/35270#issuecomment-1030566250
Comment:
I've attempted to take a look at this and tried to build it by hand (manually running `make` from the cloned source with correct arguments set). Curiously, I seem to be running into a separate issue wherein the make build script is attempting but failing to detect/load/symlink the `libblastrampoline.so` library, even after I built and installed the `libblastrampoline` package included in this PR.
I'm not sure why--my best attempt at reading the Makefile to figure out what's happening seems to point to it using `libwhich` to locate libraries; when I try to manually run `libwhich -p libblastrampoline.so`, I get
```
failed to open library: /usr/lib/libblastrampoline.so: undefined symbol: f2c_sdot_64_
```
which suggests something additionally may be broken with the current state of the libblastrampoline package. I doubt that's the same issue @non-Jedi you're facing with the `USE_*` variables getting ignored, but it seems to be yet another barrier in getting things to build correctly. Have you encountered this?
next prev parent reply other threads:[~2022-02-05 7:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35270@inbox.vuxu.org>
2022-01-30 8:23 ` kwshi
2022-01-30 13:45 ` Piraty
2022-01-30 17:33 ` Piraty
2022-01-30 17:50 ` Piraty
2022-01-30 18:41 ` non-Jedi
2022-02-04 2:36 ` non-Jedi
2022-02-04 2:38 ` [PR PATCH] [Updated] " non-Jedi
2022-02-05 4:51 ` non-Jedi
2022-02-05 4:53 ` non-Jedi
2022-02-05 4:55 ` non-Jedi
2022-02-05 4:57 ` non-Jedi
2022-02-05 4:57 ` non-Jedi
2022-02-05 7:03 ` kwshi [this message]
2022-02-22 19:06 ` [PR REVIEW] " ahesford
2022-02-22 19:06 ` ahesford
2022-02-22 19:06 ` ahesford
2022-02-25 5:52 ` Rabioli
2022-04-21 21:04 ` Piraty
2022-07-06 22:31 ` Piraty
2022-10-05 2:13 ` github-actions
2022-10-13 13:23 ` Piraty
2022-10-13 13:23 ` [PR PATCH] [Closed]: " Piraty
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=20220205070336.qC0gfBs6eKUxxcOW2Q7hHi2DAEd8adPxdXyT07T5TUI@z \
--to=kwshi@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).