From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python36-wx 4.0.7.post2
Date: Thu, 11 Jun 2020 17:03:16 +0100 [thread overview]
Message-ID: <AM0PR05MB4898018426DCBCFD07D7E80AE7800@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <14fef64e-0fa5-1c78-e355-7f2e934c4c32@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1597 bytes --]
On 11/06/2020 16:19, Marco Atzeri via Cygwin-apps wrote:
> On 10.06.2020 11:34, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Yeah. There's also a problem with the dev package I think, because
>> -lpython3.8m can't find the library, and python3.8m doesn't seem to
>> exist as a command. I might just be being a doofus though so I'll double
>> check that I installed the right packages.
>
> on python 3.8 they should be
> -lpython3.8 and python3.8
>
> You can use pkconfig to recover it
>
> $ pkg-config --libs python-3.8
> -lpython3.8
>
> $ pkg-config --libs python-3.7
> -lpython3.7m
>
Ah, thank you, that makes sense.
I have now built the packages for python 3.7 as well, from the same
source package. Your idea worked great :)
The new ones are available at the same place as before:
https://www.hamishmb.com/files/cygwin-temp/
All seems to be working okay for me, but there are some notes/questions
I have:
- I get errors from python3.cygclass at the start of every build saying
it can't find "python3-config" - looks to be a missing
symlink/misconfigured cygclass script?
- On 32-bit Cygwin, stripping the debug symbols with objdump.exe from
the libraries takes an extremely long time - I reckon 3-4 times slower
than on 64-bit, at least. It's kind of prohibitively slow, does anyone
know why?
- On 32-bit Cygwin, I tend to get fork errors when running the wxPython
demo, but not on 64-bit (identical build options). Is this likely the
32-bit fork bug mentioned on Cygwin's home page, or a problem with my
installation/setup?
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-11 16:03 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 [this message]
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
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=AM0PR05MB4898018426DCBCFD07D7E80AE7800@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).