From: mnabid <mnabid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: nautilus-python-1.2.3
Date: Mon, 01 Jun 2020 03:18:59 +0200 [thread overview]
Message-ID: <20200601011859.2_P80XNQWugaaG3rWUmibpmNqyjXSLHz7PBBcUN6Jls@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20398@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
There is an updated pull request by mnabid against master on the void-packages repository
https://github.com/mnabid/void-packages nautilus-python
https://github.com/void-linux/void-packages/pull/20398
New package: nautilus-python-1.2.3
If cross compiling, I get this error in configure:
```
configure:9474: checking for headers required to compile python extensions
configure:9530: armv7l-linux-gnueabihf-cpp -I/usr/include/python3.8 -I/usr/include/python3.8 conftest.c
In file included from /usr/include/python3.8/Python.h:63,
from conftest.c:23:
/usr/include/python3.8/pyport.h:726:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
726 | #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
```
**Added `nocross` flag as I'm stuck with this error now.**
I've submitted an issue [here](https://gitlab.gnome.org/GNOME/nautilus-python/-/issues/11).
A patch file from https://github.com/void-linux/void-packages/pull/20398.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nautilus-python-20398.patch --]
[-- Type: text/x-diff, Size: 1290 bytes --]
From 501420c953fa60420fb4bd17f264f3c6e67a2f34 Mon Sep 17 00:00:00 2001
From: Nafis <mnabid.25@outlook.com>
Date: Thu, 26 Mar 2020 13:50:36 +0600
Subject: [PATCH] New package: nautilus-python-1.2.3
---
srcpkgs/nautilus-python/template | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 srcpkgs/nautilus-python/template
diff --git a/srcpkgs/nautilus-python/template b/srcpkgs/nautilus-python/template
new file mode 100644
index 00000000000..7a32e9e6617
--- /dev/null
+++ b/srcpkgs/nautilus-python/template
@@ -0,0 +1,17 @@
+# Template file for 'nautilus-python'
+pkgname=nautilus-python
+version=1.2.3
+revision=1
+archs=noarch
+build_style=gnu-configure
+configure_args="--enable-gtk-doc PYTHON=python3"
+hostmakedepends="automake libtool pkg-config which"
+makedepends="python3-devel python3-gobject-devel gtk-doc nautilus-devel"
+depends="nautilus python3-gobject"
+short_desc="Python bindings for the Nautilus extension framework"
+maintainer="Nafis <mnabid.25@outlook.com>"
+license="GPL-2.0-or-later"
+homepage="https://wiki.gnome.org/Projects/NautilusPython"
+distfiles="${GNOME_SITE}/${pkgname}/${version%.*}/${pkgname}-${version}.tar.xz"
+checksum=073ce0297282259937ab473d189b97a04f42b97197c9292fc3bde9d135282098
+nocross="could not find Python headers"
prev parent reply other threads:[~2020-06-01 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20398@inbox.vuxu.org>
2020-04-02 9:55 ` mnabid
2020-04-16 9:21 ` mnabid
2020-04-17 16:39 ` mnabid
2020-04-24 17:19 ` mnabid
2020-04-24 22:31 ` mnabid
2020-05-06 17:22 ` mnabid
2020-06-01 1:18 ` mnabid [this message]
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=20200601011859.2_P80XNQWugaaG3rWUmibpmNqyjXSLHz7PBBcUN6Jls@z \
--to=mnabid@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).