From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] [WIP] octave: update to 6.1.0.
Date: Tue, 30 Mar 2021 20:35:20 +0200 [thread overview]
Message-ID: <20210330183520.xXBtIoq9Q9_92T9HuIqe2h_Mfh18QQZ5Uhv6U0Si63A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27775@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/27775#discussion_r604341393
Comment:
openblas has:
```
case "${XBPS_TARGET_MACHINE}" in
armv5*) make_build_args+=" TARGET=ARMV5" ;;
armv6*) make_build_args+=" TARGET=ARMV6" ;;
armv7*) make_build_args+=" TARGET=ARMV7" ;;
aarch64*) make_build_args+=" TARGET=ARMV8 DYNAMIC_ARCH=1" ;;
i686*) make_build_args+=" BINARY=32 TARGET=GENERIC DYNAMIC_ARCH=1" ;;
x86_64*) make_build_args+=" BINARY=64 TARGET=GENERIC DYNAMIC_ARCH=1" ;;
ppc64le*) make_build_args+=" TARGET=POWER8 DYNAMIC_ARCH=1" ;;
ppc64*) make_build_args+=" TARGET=PPC970MP" ;; # dynamic arch broken for <power6
ppc*) make_build_args+=" TARGET=PPCG4" ;;
mips*) broken="Not supported" ;;
*) broken="Add your CPU" ;;
esac
```
which would mean that eventual `riscv` target would be broken by default, for example, and would block octave from being built instead of building it with `lapack`. I think listing where it's known to work is a bit more correct.
next prev parent reply other threads:[~2021-03-30 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 23:21 [PR PATCH] " olafmersmann
2021-02-15 4:00 ` ericonr
2021-02-15 4:01 ` ericonr
2021-02-24 8:47 ` [PR PATCH] [Updated] " olafmersmann
2021-03-28 18:22 ` [PR REVIEW] " Piraty
2021-03-28 18:22 ` Piraty
2021-03-28 18:22 ` Piraty
2021-03-30 18:35 ` ericonr [this message]
2021-03-30 18:37 ` [PR REVIEW] " ericonr
2021-03-30 18:37 ` ericonr
2021-03-30 18:37 ` ericonr
2021-03-31 21:39 ` [PR REVIEW] [WIP] octave: update to 6.2.0 olafmersmann
2021-08-11 2:29 ` [PR PATCH] [Updated] " ericonr
2021-08-11 2:44 ` ericonr
2021-08-11 2:59 ` [PR PATCH] [Merged]: " ericonr
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=20210330183520.xXBtIoq9Q9_92T9HuIqe2h_Mfh18QQZ5Uhv6U0Si63A@z \
--to=ericonr@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).