From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python36-wx 4.0.7.post2
Date: Wed, 17 Jun 2020 09:41:17 +0100 [thread overview]
Message-ID: <AM0PR05MB4898023484261B0C477ED5BAE79A0@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <87h7vcxk11.fsf@Rainer.invalid>
[-- Attachment #1.1.1: Type: text/plain, Size: 1032 bytes --]
On 15/06/2020 19:26, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Turns out just running "rebaseall" worked for me. I don't get any
>> fork-related warnings/errors any more.
> No it doesn't, it's a mere coincidence that it worked in your case. You
> shouldn't manually run rebaseall on Cygwin at all in fact, setup
> perpetual postinstall actions take care of maintaing the rebase map.
> If you ever have reason to believe that the rebase map needs a complete
> rebuild, run "rebase-trigger full" and then run setup again.
>
> Fitting newly built DLL into the rebase map is correctly done by an
> ephemeral rebase like the script Marco has shown you does.
Good to know and thanks for the script Marco, seems to work well for me.
The only patch Fedora seems to be using is one to disable the bundled
SIP for building (which I think we need), so I believe this is now
finished. Do I need to rebuild against the new version of Python that
came out a few days ago for cygwin?
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-17 8:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:52 Hamish McIntyre-Bhatty
2020-06-09 19:53 ` Marco Atzeri
2020-06-10 9:34 ` Hamish McIntyre-Bhatty
2020-06-11 15:19 ` Marco Atzeri
2020-06-11 16:03 ` Hamish McIntyre-Bhatty
2020-06-11 16:41 ` Marco Atzeri
2020-06-15 10:20 ` Hamish McIntyre-Bhatty
2020-06-15 18:26 ` Achim Gratz
2020-06-17 8:41 ` Hamish McIntyre-Bhatty [this message]
2020-06-17 19:24 ` Marco Atzeri
2020-06-17 21:23 ` Hamish McIntyre-Bhatty
2020-06-18 8:20 ` Hamish McIntyre-Bhatty
2020-06-18 9:24 ` Marco Atzeri
2020-06-18 11:31 ` Hamish McIntyre-Bhatty
2020-06-18 14:08 ` Jon Turney
2020-06-18 15:05 ` Hamish McIntyre-Bhatty
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=AM0PR05MB4898023484261B0C477ED5BAE79A0@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin-apps@cygwin.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).