Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mark some rust packages that use `ring` broken on ppc
Date: Mon, 10 Jun 2019 21:58:16 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12382@inbox.vuxu.org> (raw)

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

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

https://github.com/void-power/void-packages ring
https://github.com/void-linux/void-packages/pull/12382

mark some rust packages that use `ring` broken on ppc
These all use `ring` (directly or indirectly), a rust crypto library that only has platform specific assembly and no support for ppc platforms. I wrote WiP support for ppc* for that lib, so these are temporary, but it will probably take a while to upstream.

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

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

From 49f50ac8ac9989ce2880fb1cb0bdd6334b981400 Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Mon, 10 Jun 2019 21:34:29 +0200
Subject: [PATCH 1/3] boringtun: broken on ppc for now (ftbfs in ring)

---
 srcpkgs/boringtun/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/boringtun/template b/srcpkgs/boringtun/template
index 435900313da..73dc4cc76e4 100644
--- a/srcpkgs/boringtun/template
+++ b/srcpkgs/boringtun/template
@@ -12,6 +12,7 @@ checksum=544c72fc482b636e7f6460bfee205adafc55de534067819e4e4914980f0d1350
 
 case "$XBPS_TARGET_MACHINE" in
 	*-musl) broken="ioctl function signature differs on glibc and musl" ;;
+	ppc*) broken="ftbfs in ring" ;;
 esac
 
 post_install() {

From e13e53d58aa9f0cd2e95ec849298581f5a1c36e2 Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Mon, 10 Jun 2019 21:44:58 +0200
Subject: [PATCH 2/3] routinator: broken on ppc (ftbfs in ring)

---
 srcpkgs/routinator/template | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/srcpkgs/routinator/template b/srcpkgs/routinator/template
index 3b14fa4ce2f..44e983aff15 100644
--- a/srcpkgs/routinator/template
+++ b/srcpkgs/routinator/template
@@ -11,6 +11,10 @@ homepage="https://github.com/NLnetLabs/routinator"
 distfiles="${homepage}/archive/v${version}.tar.gz"
 checksum=00d55fcfda6bee6311304415b77347e72e6f65f5f549c57c70876234f67cc0ab
 
+case "$XBPS_TARGET_MACHINE" in
+	ppc*) broken="ftbfs in ring" ;;
+esac
+
 post_install() {
 	vlicense LICENSE
 }

From c7bd769367c76c70f200fb6c0ca280ceb997cab3 Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Mon, 10 Jun 2019 21:45:33 +0200
Subject: [PATCH 3/3] rust-sccache: broken on ppc (ftbfs in ring)

[ci skip]
---
 srcpkgs/rust-sccache/template | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/srcpkgs/rust-sccache/template b/srcpkgs/rust-sccache/template
index 016a8299c79..d577a34efdc 100644
--- a/srcpkgs/rust-sccache/template
+++ b/srcpkgs/rust-sccache/template
@@ -12,3 +12,7 @@ license="Apache-2.0"
 homepage="https://crates.io/crates/sccache"
 distfiles="https://static.crates.io/crates/sccache/sccache-${version}.crate"
 checksum=c1e914cab6496ac4ea3ef9e52b2a14661edd313ae3ecad8ce52f3a254aafcc1a
+
+case "$XBPS_TARGET_MACHINE" in
+	ppc*) broken="ftbfs in ring" ;;
+esac

             reply	other threads:[~2019-06-10 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 19:58 voidlinux-github [this message]
2019-06-12 10:47 ` [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-12382@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).