public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: josef radinger <cheese@nosuchhost.net>
To: git-commits@fedoraproject.org
Subject: [rpms/schismtracker] rawhide: try to fix build on ppc64le
Date: Fri, 12 Jun 2026 08:10:05 GMT	[thread overview]
Message-ID: <178125180562.1.7649427926298203487.rpms-schismtracker-28933b8a20c2@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/schismtracker
Branch : rawhide
Commit : 28933b8a20c27aef6131c8e706c3d8c0e561b831
Author : josef radinger <cheese@nosuchhost.net>
Date   : 2026-06-12T10:09:46+02:00
Stats  : +8/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/schismtracker/c/28933b8a20c27aef6131c8e706c3d8c0e561b831?branch=rawhide

Log:
try to fix build on ppc64le

---
diff --git a/schismtracker.spec b/schismtracker.spec
index 6983420..2c86b5c 100644
--- a/schismtracker.spec
+++ b/schismtracker.spec
@@ -41,7 +41,13 @@ mkdir auto
 
 %build
 autoreconf -i
+
+# disable altivec for now to fix compile
+
 %configure --disable-dependency-tracking \
+%ifarch ppc64le
+--disable-altivec \
+%endif
 %if 0%{?_without_x:1}
 --with-x=no \
 %endif
@@ -69,9 +75,10 @@ desktop-file-validate %{buildroot}%{_datadir}/applications/schism.desktop
 %{_datadir}/pixmaps/schism*.png
 
 %changelog
-* Thu May 28 2026 josef radinger <cheese@nosuchhost.net> - 20260524-2
+* Fri June 12 2026 josef radinger <cheese@nosuchhost.net> - 20260524-2
 - add Patch1 to fix compilation with ppc64le
   https://github.com/schismtracker/schismtracker/commit/ee6798584b26856260bccca7b8f7730b221b1c0e.patch
+- try to fix compile by disabling altivec on ppc64le
 
 * Wed May 27 2026 josef radinger <cheese@nosuchhost.net> - 20260524-1
 - bump version

                 reply	other threads:[~2026-06-12  8:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178125180562.1.7649427926298203487.rpms-schismtracker-28933b8a20c2@fedoraproject.org \
    --to=cheese@nosuchhost.net \
    --cc=git-commits@fedoraproject.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