From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] build-helper/numpy: fix typo
Date: Tue, 18 Jan 2022 13:01:19 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35108@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages numpy-helper-typo
https://github.com/void-linux/void-packages/pull/35108
build-helper/numpy: fix typo
None
A patch file from https://github.com/void-linux/void-packages/pull/35108.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-numpy-helper-typo-35108.patch --]
[-- Type: text/x-diff, Size: 939 bytes --]
From f6d6118362c833ae5440f495f26868c4906d5314 Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Tue, 18 Jan 2022 23:00:16 +1100
Subject: [PATCH] build-helper/numpy: fix typo
---
common/build-helper/numpy.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/build-helper/numpy.sh b/common/build-helper/numpy.sh
index 3731885a04e7..74c642116529 100644
--- a/common/build-helper/numpy.sh
+++ b/common/build-helper/numpy.sh
@@ -17,7 +17,7 @@ if [ "$CROSS_BUILD" ]; then
fi
# python3-setuptools finds numpy libs and headers on the host first;
- # addding search paths up front allows the target to take priority
+ # adding search paths up front allows the target to take priority
CFLAGS+=" -I${XBPS_CROSS_BASE}/${py3_sitelib}/numpy/core/include"
LDFLAGS+=" -L${XBPS_CROSS_BASE}/${py3_sitelib}/numpy/core/lib"
LDFLAGS+=" -L${XBPS_CROSS_BASE}/${py3_sitelib}/numpy/random/lib"
next reply other threads:[~2022-01-18 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 12:01 unspecd [this message]
2022-01-18 19:19 ` [PR PATCH] [Merged]: " ericonr
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-35108@inbox.vuxu.org \
--to=unspecd@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).