From: Marcel van der Boom <marcel@van-der-boom.nl>
To: 56884@debbugs.gnu.org
Cc: Marcel van der Boom <marcel@van-der-boom.nl>,
Thiago Jung Bauermann <bauermann@kolabnow.com>
Subject: [bug#56884] [PATCH] Make x265 build on ppc64le
Date: Wed, 10 Aug 2022 09:19:02 +0200 [thread overview]
Message-ID: <097e5d484b14e0777f26bfd5c34b76189b828b8c.1660115870.git.marcel@van-der-boom.nl> (raw)
In-Reply-To: <f7be730ee74999da0f20b44c94c805681a194730.1659442047.git.marcel@van-der-boom.nl>
* gnu/packages/video.scm: disable ALTIVEC for target-ppc64le
Build produces many errors. The altivec code needs adjusting each type of
POWER processor specifically.
---
gnu/packages/video.scm | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
index 04049fd9c8..bf033c7d84 100644
--- a/gnu/packages/video.scm
+++ b/gnu/packages/video.scm
@@ -1252,6 +1252,10 @@ (define-public x265
,@(if (target-aarch64?)
'("-DENABLE_ASSEMBLY=OFF")
'())
+ ;; Altivec code produces many build errors
+ ,@(if (target-ppc64le?)
+ '("-DENABLE_ALTIVEC=OFF")
+ '())
"-DHIGH_BIT_DEPTH=ON"
"-DEXPORT_C_API=OFF"
"-DENABLE_CLI=OFF"
@@ -1272,6 +1276,10 @@ (define-public x265
,@(if (target-aarch64?)
'("-DENABLE_ASSEMBLY=OFF")
'())
+ ;; Altivec code produces many build errors
+ ,@(if (target-ppc64le?)
+ '("-DENABLE_ALTIVEC=OFF")
+ '())
"-DHIGH_BIT_DEPTH=ON"
"-DEXPORT_C_API=OFF"
"-DENABLE_CLI=OFF"
--
2.37.1
next prev parent reply other threads:[~2022-08-10 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 12:10 [bug#56884] [PATCH] Make x265 build on ppc64le Marcel van der Boom
2022-08-09 8:02 ` Marcel van der Boom
2022-08-10 2:16 ` Thiago Jung Bauermann via Guix-patches via
2022-08-10 7:19 ` Marcel van der Boom [this message]
2022-08-11 2:15 ` Thiago Jung Bauermann via Guix-patches via
2022-08-11 7:45 ` bug#56884: " Mathieu Othacehe
2022-08-11 14:50 ` [bug#56884] " Thiago Jung Bauermann via Guix-patches via
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=097e5d484b14e0777f26bfd5c34b76189b828b8c.1660115870.git.marcel@van-der-boom.nl \
--to=marcel@van-der-boom.nl \
--cc=56884@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.