From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] i2c-tools: change upstream and add python subpkg
Date: Sun, 22 May 2022 21:33:22 +0200 [thread overview]
Message-ID: <20220522193322.f-MjCWyfHDzs4xFbtiVkL58GVVrJUxNJ1HTAzKsEhpY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36304@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
New review comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/36304#discussion_r878915734
Comment:
```suggestion
if [ -n "$CROSS_BUILD" ]; then
export PYPREFIX="$XBPS_CROSS_BASE"
export CFLAGS+=" -I${XBPS_CROSS_BASE}/${py3_inc} -I${XBPS_CROSS_BASE}/usr/include"
export LDFLAGS+=" -L${XBPS_CROSS_BASE}/${py3_lib} -L${XBPS_CROSS_BASE}/usr/lib"
export CC="${XBPS_CROSS_TRIPLET}-gcc -pthread $CFLAGS $LDFLAGS"
export LDSHARED="${CC} -shared $LDFLAGS"
export PYTHONPATH="${XBPS_CROSS_BASE}/${py3_lib}"
for f in ${XBPS_CROSS_BASE}/${py3_lib}/_sysconfigdata_*; do
f=${f##*/}
_PYTHON_SYSCONFIGDATA_NAME=${f%.py}
done
export _PYTHON_SYSCONFIGDATA_NAME
fi
```
i think this should work
next prev parent reply other threads:[~2022-05-22 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 21:23 [PR PATCH] " 0x5c
2022-03-23 21:44 ` leahneukirchen
2022-03-29 11:11 ` [PR PATCH] [Updated] " 0x5c
2022-03-29 11:16 ` 0x5c
2022-05-07 9:11 ` [PR PATCH] [Updated] " 0x5c
2022-05-07 9:26 ` 0x5c
2022-05-07 22:55 ` [PR PATCH] [Updated] " 0x5c
2022-05-22 19:33 ` classabbyamp [this message]
2022-05-22 19:34 ` [PR REVIEW] " classabbyamp
2022-05-23 4:52 ` [PR PATCH] [Updated] " 0x5c
2022-05-23 4:57 ` [PR REVIEW] " 0x5c
2022-05-23 4:59 ` 0x5c
2022-05-23 4:59 ` 0x5c
2022-05-27 22:54 ` [PR PATCH] [Updated] " 0x5c
2022-05-27 23:05 ` 0x5c
2022-05-27 23:22 ` 0x5c
2022-06-12 1:14 ` 0x5c
2022-06-12 1:19 ` 0x5c
2022-06-13 8:27 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220522193322.f-MjCWyfHDzs4xFbtiVkL58GVVrJUxNJ1HTAzKsEhpY@z \
--to=classabbyamp@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).