public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Lemures Lemniscati <lemures.lemniscati@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: g-ir-scanner fails with python-3.8
Date: Thu, 12 Jan 2023 19:50:21 +0000	[thread overview]
Message-ID: <e62a6da6-bbe9-46c4-6960-5167aa5360db@dronecode.org.uk> (raw)
In-Reply-To: <20210523140358.9877.50F79699@gmail.com>

On 23/05/2021 06:04, Lemures Lemniscati via Cygwin-apps wrote:
> On Sun, 23 May 2021 06:01:43 +0200, Marco Atzeri via Cygwin-apps
>> On 23.05.2021 05:51, Marco Atzeri wrote:
>>> On 23.05.2021 01:44, Lemures Lemniscati via Cygwin-apps wrote:
>>>> On Wed, 19 May 2021 22:09:59 +0100, Jon Turney
>>>>> On 19/05/2021 20:32, Ken Brown via Cygwin-apps wrote:
>>
>>>>
>>>> Here are patches...
>>>>
>>>> * 0002-gobject-introspection-1.54.1-4.patch:
>>>>       python3.8 is used explicitly.
>>>>         Shebangs of g-ir-doc-tool and g-ir-scanner are '/usr/bin/env
>>>> python3.8'
>>>>         _giscanner.dll is linked with libpython3.8.dll
>>>>
>>>> * 0001-Fix-a-patch-for-giscanner-shlibs.py-to-pass-a-pep8-c.patch:
>>>>       This has no effect while building.
>>>>       But needed in order to avoid an error in a test
>>>>         cygport gobject-introspection.cygport test
>>>>
[...]
> 
> 
> These patches are the last two commit from here for the time being:
> 
> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=commitdiff;h=1f435122b29fdc5a7c3f71f6da0cb28bbb843847
> 
> which forked from the gobject-introspection 1.54.1-3
> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gobject-introspection.git;a=commit;h=cd7b82d762911316ae43708b30941fea4d7f718d
> 
> Atattched files are modified files based on 1.54.1-3.
> 
> gobject-introdpection.cygport: modified.
> 1.54.1-2-cygwin.patch: removed a trailing space.
Thanks, Lem.

I've rebuilt gobject-introspection for python39, using these patches. 
Sorry that took so long to get around to.

(It would be nice to update this to a later version, but that seems to 
require glib to be updated also...)


  reply	other threads:[~2023-01-12 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 19:32 Ken Brown
2021-05-19 21:09 ` Jon Turney
2021-05-22 23:44   ` Lemures Lemniscati
2021-05-23  3:51     ` Marco Atzeri
2021-05-23  4:01       ` Marco Atzeri
2021-05-23  4:45         ` Marco Atzeri
2021-05-23  5:04         ` Lemures Lemniscati
2023-01-12 19:50           ` Jon Turney [this message]
2021-05-23  6:00     ` Brian Inglis
2021-05-23 11:50       ` Lemures Lemniscati
2021-05-23 18:17         ` Jon Turney
2021-05-23 18:13     ` Jon Turney
2021-05-19 21:21 ` Marco Atzeri

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=e62a6da6-bbe9-46c4-6960-5167aa5360db@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=lemures.lemniscati@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).