Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3: force sem_gevalue for all cross arches
Date: Tue, 16 May 2023 16:37:51 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43902@inbox.vuxu.org> (raw)

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

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

https://github.com/dkwo/void-packages py3
https://github.com/void-linux/void-packages/pull/43902

python3: force sem_gevalue for all cross arches
- I tested the changes in this PR: yes
- I built this PR locally for my native architecture, (aarch64)

As discussed in https://github.com/void-linux/void-packages/pull/43659 this is checked by compiling and running a program that won't work in cross, but we know `sem_gevalue` is ok at least on `aarch64` (to be more conservative, I could also only enable it there, rather than all arches).

cc @ahesford 

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

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

From 4f81c2fe59c2f96c568d99454e85f9f2d316a0c1 Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Tue, 16 May 2023 10:32:42 -0400
Subject: [PATCH] python3: force sem_gevalue for all cross arch

---
 srcpkgs/python3/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/python3/template b/srcpkgs/python3/template
index aebf41852764..04ef3591be55 100644
--- a/srcpkgs/python3/template
+++ b/srcpkgs/python3/template
@@ -4,7 +4,7 @@
 #
 pkgname=python3
 version=3.11.3
-revision=1
+revision=2
 build_style="gnu-configure"
 configure_args="--enable-shared --enable-ipv6
  --enable-loadable-sqlite-extensions --with-computed-gotos
@@ -39,6 +39,7 @@ alternatives="
 if [ "$CROSS_BUILD" ]; then
 	hostmakedepends+=" python3"
 	configure_args+=" --with-build-python=python3.11"
+	configure_args+=" ac_cv_broken_sem_getvalue=no"
 fi
 
 post_extract() {

             reply	other threads:[~2023-05-16 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 14:37 dkwo [this message]
2023-05-18 16:04 ` [PR PATCH] [Merged]: " ahesford
2023-05-18 16:04 ` ahesford

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-43902@inbox.vuxu.org \
    --to=dkwo@users.noreply.github.com \
    --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).