Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telegram-desktop: use libatomic on 32-bit ppc
Date: Tue, 08 Oct 2019 02:22:20 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15228@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 328 bytes --]

There is a new pull request by q66 against master on the void-packages repository

https://github.com/void-ppc/void-packages telegram
https://github.com/void-linux/void-packages/pull/15228

telegram-desktop: use libatomic on 32-bit ppc


A patch file from https://github.com/void-linux/void-packages/pull/15228.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-telegram-15228.patch --]
[-- Type: text/x-diff, Size: 724 bytes --]

From 837c0db606ada029f8bb7c23b552613f2f1dfc1f Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Tue, 8 Oct 2019 01:59:50 +0200
Subject: [PATCH] telegram-desktop: use libatomic on 32-bit ppc

[ci skip]
---
 srcpkgs/telegram-desktop/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/telegram-desktop/template b/srcpkgs/telegram-desktop/template
index 26553202409..be11cde6cfb 100644
--- a/srcpkgs/telegram-desktop/template
+++ b/srcpkgs/telegram-desktop/template
@@ -45,7 +45,8 @@ case $XBPS_TARGET_MACHINE in
 	mips*)
 		broken="unsupported"
 		;;
-	armv[56]*)
+	ppc64*) ;;
+	armv[56]*|ppc*)
 		makedepends+=" libatomic-devel"
 		configure_args+=" -DUSE_LIBATOMIC=ON"
 		;;

             reply	other threads:[~2019-10-08  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08  0:22 voidlinux-github [this message]
2019-10-08 18:19 ` [PR PATCH] [Merged]: " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15228@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).