From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] skalibs: do not unconditionally set archs
Date: Fri, 03 May 2019 18:33:56 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11465@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
There is a new pull request by q66 against master on the void-packages repository
https://github.com/void-ppc64/void-packages skalibs
https://github.com/void-linux/void-packages/pull/11465
skalibs: do not unconditionally set archs
There is no need to break native builds too when they work perfectly fine. Also reenable armv6.
@stenstorp next time please mark things properly like this, I'm trying to get this right across the repo...
A patch file from https://github.com/void-linux/void-packages/pull/11465.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-skalibs-11465.patch --]
[-- Type: application/text/x-diff, Size: 1325 bytes --]
From 86346cf53353922cd79366d69782271549f05a68 Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Fri, 3 May 2019 18:28:22 +0200
Subject: [PATCH] skalibs: do not unconditionally set archs
There is no need to break native builds too when they work
perfectly fine. Also reenable armv6.
---
srcpkgs/skalibs/template | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/skalibs/template b/srcpkgs/skalibs/template
index c90afb3b855..35bc0470df5 100644
--- a/srcpkgs/skalibs/template
+++ b/srcpkgs/skalibs/template
@@ -3,7 +3,6 @@ pkgname=skalibs
version=2.8.0.1
revision=1
_sysdepspkg=skaware-void-sysdeps
-archs="aarch64* armv7l* i686 x86_64*"
build_style=configure
configure_args="--libdir=/usr/lib --enable-static --enable-shared --enable-clock
--enable-monotonic --enable-force-devr --datadir=/usr/share/$pkgname --libdir=/usr/lib
@@ -21,6 +20,11 @@ if [ "$CROSS_BUILD" ]; then
distfiles+=" https://github.com/CMB/${_sysdepspkg}/archive/${version}.tar.gz"
checksum+=" 6d0f62109f22edfa1e8e0f1885bff705a2ce0c3588592692afbddeb6d691d7f7"
configure_args+=" --with-sysdeps=../${_sysdepspkg}-${version}/${XBPS_CROSS_TRIPLET}"
+
+ case "$XBPS_TARGET_MACHINE" in
+ aarch64*|armv6*|armv7l*|i686|x86_64*) ;;
+ *) nocross="Missing cross sysdeps" ;;
+ esac
fi
post_install() {
next reply other threads:[~2019-05-03 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 16:33 voidlinux-github [this message]
2019-05-03 18:14 ` [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-11465@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).