From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: new package: pypy3.7
Date: Sat, 23 Oct 2021 17:27:12 +0200 [thread overview]
Message-ID: <20211023152712.mYAFMYqlKtAn_LwXspkZCRxprjsVaZhE6n3T4IGe3ts@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33712@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/33712#issuecomment-950168510
Comment:
Thanks, I can include those changes.
The `musl` version fails with
```
[platform:Error] pytime.c:531:1: error: conflicting types for '_PyTime_AsTimeval'
[platform:Error] 531 | _PyTime_AsTimeval(_PyTime_t t, struct timeval *tv, _PyTime_round_t round)
[platform:Error] | ^~~~~~~~~~~~~~~~~
[platform:Error] In file included from /builddir/pypy3.7-v7.3.5-src/rpython/../pypy/module/cpyext/include/Python.h:79,
[platform:Error] from pytime.c:1:
[platform:Error] /builddir/pypy3.7-v7.3.5-src/rpython/../pypy/module/cpyext/include/pytime.h:125:17: note: previous declaration of '_PyTime_AsTimeval' was here
[platform:Error] 125 | PyAPI_FUNC(int) _PyTime_AsTimeval(_PyTime_t t,
[platform:Error] | ^~~~~~~~~~~~~~~~~
[platform:Error] pytime.c:537:1: error: conflicting types for '_PyTime_AsTimeval_noraise'
[platform:Error] 537 | _PyTime_AsTimeval_noraise(_PyTime_t t, struct timeval *tv, _PyTime_round_t round)
[platform:Error] | ^~~~~~~~~~~~~~~~~~~~~~~~~
[platform:Error] In file included from /builddir/pypy3.7-v7.3.5-src/rpython/../pypy/module/cpyext/include/Python.h:79,
[platform:Error] from pytime.c:1:
[platform:Error] /builddir/pypy3.7-v7.3.5-src/rpython/../pypy/module/cpyext/include/pytime.h:130:17: note: previous declaration of '_PyTime_AsTimeval_noraise' was here
[platform:Error] 130 | PyAPI_FUNC(int) _PyTime_AsTimeval_noraise(_PyTime_t t,
[platform:Error] | ^~~~~~~~~~~~~~~~~~~~~~~~~
[platform:Error] make: *** [Makefile:950: pytime.o] Error 1
[platform:Error] make: *** Waiting for unfinished jobs....
```
Maybe there's another way to bootstrap it, without using `python2`?
next prev parent reply other threads:[~2021-10-23 15:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 13:07 [PR PATCH] " dkwo
2021-10-23 13:19 ` [PR REVIEW] " Chocimier
2021-10-23 13:19 ` Chocimier
2021-10-23 15:27 ` dkwo [this message]
2021-10-23 16:34 ` [PR PATCH] [Updated] " dkwo
2021-10-26 9:03 ` dkwo
2021-10-26 18:41 ` Chocimier
2021-10-26 18:42 ` [PR REVIEW] " Chocimier
2021-10-26 18:42 ` Chocimier
2021-10-27 9:50 ` [PR PATCH] [Updated] " dkwo
2021-10-27 9:51 ` [PR REVIEW] " dkwo
2021-10-27 19:05 ` [PR PATCH] [Updated] " dkwo
2021-10-28 11:40 ` dkwo
2021-10-28 11:42 ` dkwo
2021-12-16 0:51 ` EliteTK
2021-12-16 1:01 ` ahesford
2021-12-16 2:32 ` EliteTK
2021-12-16 2:33 ` EliteTK
2021-12-16 3:06 ` ahesford
2021-12-16 9:04 ` dkwo
2022-01-02 8:34 ` dkwo
2022-01-02 8:34 ` [PR PATCH] [Closed]: " dkwo
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=20211023152712.mYAFMYqlKtAn_LwXspkZCRxprjsVaZhE6n3T4IGe3ts@z \
--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).