Re: GNU make losing jobserver tokens
On Sat, 30 Apr 2022 17:51:03 -0400 Ken Brown wrote: > On 4/29/2022 5:10 AM, Takashi Yano wrote: > > On Thu, 28 Apr 2022 17:32:22 +0200 > > I tried to move sigproc_init() call from dll_crt0_0() to > > fork::child() for 64bit cygwin, however, that causes hang > > at cygwin startup. > > > > Am I missing somehting? > > I've never looked into the Cygwin startup code, so just ignore me if what I > say > is nonsense. > > Currently sigproc_init is called either from dll_crt0_0 or from dll_crt0_1, > depending on the value of dynamically_loaded. What would happen if you > always > call it from dll_crt0_1, right after > >cygwin_finished_initializing = true; Thanks for the advice. That causes hang on cygwin startup due to fork() fail :( -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: GNU make losing jobserver tokens
On 4/29/2022 5:10 AM, Takashi Yano wrote: On Thu, 28 Apr 2022 17:32:22 +0200 I tried to move sigproc_init() call from dll_crt0_0() to fork::child() for 64bit cygwin, however, that causes hang at cygwin startup. Am I missing somehting? I've never looked into the Cygwin startup code, so just ignore me if what I say is nonsense. Currently sigproc_init is called either from dll_crt0_0 or from dll_crt0_1, depending on the value of dynamically_loaded. What would happen if you always call it from dll_crt0_1, right after cygwin_finished_initializing = true; Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] duplicity 0.7.19-1{i686,x86_64}
The following packages have been uploaded to the Cygwin distribution * duplicity-0.7.19-1 Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. This duplicity is the last stable 0.7 version (2019/04/19), replacement for quite old v0.7.11 (2016/12/31) . After some testing period it will be moved from test to release. Any feedback appreciated. This is probably the last i686 version, following 0.8 will be x86_64 only. Please send questions or concerns to the main Cygwin mailing list as usual. Libor -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe:" tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.comcygwin.com If you need more information on unsubscribing, start reading here: https://sourceware.org/lists.html#unsubscribe -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] python-fasteners 0.16.3-1
The following packages have been uploaded to the Cygwin distribution: * python27-fasteners-0.16.3-1 * python38-fasteners-0.16.3-1 * python39-fasteners-0.16.3-1 Python standard library provides a lock for threads (both a reentrant one, and a non-reentrant one, see below). Fasteners extends this, and provides a lock for processes, as well as Reader Writer locks for both threads and processes. This package is a requirement for `duplicity` package, see other following duplicity announcement. Please send questions or concerns to the main Cygwin mailing list as usual. Libor -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe:" tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.comcygwin.com If you need more information on unsubscribing, start reading here: https://sourceware.org/lists.html#unsubscribe -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
duplicity 0.7.19-1{i686,x86_64}
The following packages have been uploaded to the Cygwin distribution * duplicity-0.7.19-1 Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. This duplicity is the last stable 0.7 version (2019/04/19), replacement for quite old v0.7.11 (2016/12/31) . After some testing period it will be moved from test to release. Any feedback appreciated. This is probably the last i686 version, following 0.8 will be x86_64 only. Please send questions or concerns to the main Cygwin mailing list as usual. Libor -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe:" tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.comcygwin.com If you need more information on unsubscribing, start reading here: https://sourceware.org/lists.html#unsubscribe
python-fasteners 0.16.3-1
The following packages have been uploaded to the Cygwin distribution: * python27-fasteners-0.16.3-1 * python38-fasteners-0.16.3-1 * python39-fasteners-0.16.3-1 Python standard library provides a lock for threads (both a reentrant one, and a non-reentrant one, see below). Fasteners extends this, and provides a lock for processes, as well as Reader Writer locks for both threads and processes. This package is a requirement for `duplicity` package, see other following duplicity announcement. Please send questions or concerns to the main Cygwin mailing list as usual. Libor -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe:" tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.comcygwin.com If you need more information on unsubscribing, start reading here: https://sourceware.org/lists.html#unsubscribe
Re: Window flickering problem in XWin multiwindow mode
On 26/04/2022 04:53, S.J. Luo wrote: I have some EDA tools running on a Linux machine and display on my Windows PC using xorg-server-21.1.3 XWin multiwindow mode Sometimes the application window flickers forever for an unknown reason. The problem became more severe after my PC upgrade to Windows10. Googling the problem, I did not find such issue reported. I decided to take advantage of open source nature and solve it by myself. After re-compiling and debugging, I found a calling loop triggered. Here I eliminate the detail of the cause. I may write later if someone requires. Knowing the root cause, I am now able to demonstrate the issue with a small test case as well as a patch that works for me. Both are attached below. Thanks very much for taking the time to look into this, and writing a patch. I will apply it. But I'd like to add a bit more commentary, which perhaps you can supply, about the analysis you did to determine: 1. how the code is misbehaving 2. how this change remedies that 3. how this change doesn't effect anything else What your fix does is examine the queue of pending WM messages to determine if there are any more pending for the window receiving a WM_WM_CHANGE_STATE message, and if there are, ignore it. It seems to me that is error prone, in a couple of ways: 1. it should check the message type as well, as e.g. a pending message of a different type could cause a WM_WM_CHANGE_STATE message to be ignored. 2. even then, assuming that successive WM_WM_CHANGE_STATE messages cancel out each other isn't always true e.g. consider a sequence of _NET_WM_STATE_ADD _NET_WM_STATE_MAXIMIZED_VERT followed by _NET_WM_STATE_ADD _NET_WM_STATE_MAXIMIZED_HORZ. If you were to send other patches in future, please send them as attachments, or even better, using git format-patch/git send-email, as that makes it much easier to apply them without white-space damage and with correct attribution. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [Attn: mercurial maintainer] hg fails with python3.9
On 29/04/2022 15:11, Jari Aalto wrote: On 2022-04-29 12:23, Jon Turney wrote: libdir = '../lib/python3.8/site-packages' This causes hg to fail as follows if /usr/bin/python3 points to python3.9: ERROR: package 'mercurial' version '5.7-3' is most recent non-test version, but version '6.0-1' is curr This error is trying to tell you "version 6.0-1 exists, so the version you are uploading won't be installed for anyone who already has that higher version number installed, so maybe this isn't what you want to do". mercurial version 6.0-1 does exist, for x86_64 only, dated 2021-11-25. My mistake. I had the development environment in wrong server, so only 5.7 was in there and I forgot to check the latest in Cygwin. 6.1.1-1 uploaded No problem. I'll see if I can improve that error message sometime. I notice that mercurial appears to be pure python, so maybe we can upload it as noarch in future? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Slow cygwin executable start up
I am experiencing a problem with Cygwin on my Dell 7590. There is a multi-second delay when starting a cygwin program from a mintty window, but only the first time that a program is run. E.g. if run openssl version, then sometimes there is a delay before anything is outputted. If I run the command again, there is no delay. I ran a test with strace, and I believe the delay occurs during the initial loading of the cygwin dlls: --- Process 6232 created --- Process 6232 loaded C:\Windows\System32\ntdll.dll at 7ffe3b4c --- Process 6232 loaded C:\Windows\System32\kernel32.dll at 7ffe3a66 --- Process 6232 loaded C:\Windows\System32\KernelBase.dll at 7ffe38c6 --- Process 6232 thread 24052 created --- Process 6232 thread 28400 created --- Process 6232 thread 2788 created --- Process 6232 loaded C:\cygwin64\bin\cygssl-1.1.dll at 0003f7a6 --- Process 6232 loaded C:\cygwin64\bin\cygcrypto-1.1.dll at 0003fa54 --- Process 6232 loaded C:\cygwin64\bin\cygwin1.dll at 00018004 --- Process 6232 loaded C:\cygwin64\bin\cygz.dll at 0003f732 --- Process 6232 loaded C:\cygwin64\bin\cygwin1.dll at 00da Can anyone suggest why this is happening? The version of cygwin is: $ uname -r 3.2.0(0.340/5/3) By the way, I don't see this on my older PC, it's version of cygwin is: 3.1.7(0.340/5/3) I don't really want to upgrade my older PC to the latest cygwin to test if the 3.2 version is the culprit or not. I also upgraded from windows 10 to windows 11 on the PC experiencing the slow start issue, and that didn't have any effect on the problem. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: {,mingw-{i686,x86_64}-}pcre2-10.40-1
The PCRE2 library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl, with just a few differences. This the latest upstream release with bugfixes, cleanups and an update to Unicode handling. The following packages have been uploaded to the Cygwin distribution: pcre2-10.40-1 libpcre2-10.40-1 libpcre2_16_0-10.40-1 libpcre2_32_0-10.40-1 libpcre2-posix3-10.40-1 libpcre2-devel-10.40-1 libpcre2-doc-10.40-1 mingw-i686-pcre2-10.40-1 mingw-x86_64-pcre2-10.40-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: {,mingw-{i686,x86_64}-}pcre2-10.40-1
The PCRE2 library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl, with just a few differences. This the latest upstream release with bugfixes, cleanups and an update to Unicode handling. The following packages have been uploaded to the Cygwin distribution: pcre2-10.40-1 libpcre2-10.40-1 libpcre2_16_0-10.40-1 libpcre2_32_0-10.40-1 libpcre2-posix3-10.40-1 libpcre2-devel-10.40-1 libpcre2-doc-10.40-1 mingw-i686-pcre2-10.40-1 mingw-x86_64-pcre2-10.40-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-DateTime-1.58-1 noarch -- perl-DateTime-Locale-1.35-1 perl-File-Listing-6.15-1 perl-JSON-PP-4.08-1 perl-libwww-perl-6.64-1 perl-List-UtilsBy-0.12-1 perl-Mojolicious-9.25-1 perl-Test-Harness-3.44-1 perl-Text-Template-1.61-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-DateTime-1.58-1 noarch -- perl-DateTime-Locale-1.35-1 perl-File-Listing-6.15-1 perl-JSON-PP-4.08-1 perl-libwww-perl-6.64-1 perl-List-UtilsBy-0.12-1 perl-Mojolicious-9.25-1 perl-Test-Harness-3.44-1 perl-Text-Template-1.61-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
