Re: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test)
Hi Takashi, Takashi Yano via Cygwin wrote: On Wed, 3 Nov 2021 22:04:05 +0900 Takashi Yano wrote: On Wed, 3 Nov 2021 02:59:38 -0700 Mark Geisert wrote: The following packages have been uploaded to the Cygwin distribution: * cygutils-1.4.16-8 * cygutils-extra-1.4.16-8 * cygutils-x11-1.4.16-8 [...] This update also provides a new feature: robust copy/paste between 32-bit and 64-bit Cygwin environments, provided both are running 3.3.0 (Test) or higher. I have tested the 1.4.16-8 (Test) and confirmed the following cases work as expected. 1) Charset conversion under locale other than UTF-8. 2) putclip error. 3) 32-bit and 64-bit inter-operability. One small thing I noticed is that time stamp of /dev/clipboard is broken with the following scenario. 1) Run 'echo A | putclip' in 32bit cygwin 2) Run 'ls -l /dev/clipboard' in 64bit cygwin Yes indeed :-() I'll debug this. Thanks for the report. ..mark -- 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: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
On Thu, 4 Nov 2021 10:02:55 -0500 Brian wrote: > GCM (Git Credential Manager) - Core fails to properly authenticate with > previously stored credentials under the latest 3.3.0 release version of the > Cygwin DLL (the bug itself and steps to recreate was originally submitted > to the GCM-Core team here: > https://github.com/microsoft/Git-Credential-Manager-Core/issues/509). By > replacing the Cygwin DLL with the 0913 snapshot, the problem no longer > occurs. One of the GCM-Core devs suggested it might be a regression issue > in the DLL. Unfortunately, I don't have the C chops to explore this > further. Could you please provide the detailed steps to reproduce your problem? -- 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: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test)
On Wed, 3 Nov 2021 22:04:05 +0900 Takashi Yano wrote: > On Wed, 3 Nov 2021 02:59:38 -0700 > Mark Geisert wrote: > > The following packages have been uploaded to the Cygwin distribution: > > > > * cygutils-1.4.16-8 > > * cygutils-extra-1.4.16-8 > > * cygutils-x11-1.4.16-8 > > > > This update fixes a couple issues with getclip and putclip, namely: > > 1) Mistakenly assuming charset is always UTF-8, > > 2) Opening and closing the clipboard multiple times (putclip only), > >sometimes causing ERROR_ACCESS_DENIED. > > Thanks to Takashi Yano for bug reports with testcases, and especially > > the patches! > > > > This update also provides a new feature: robust copy/paste between > > 32-bit and 64-bit Cygwin environments, provided both are running > > 3.3.0 (Test) or higher. > > I have tested the 1.4.16-8 (Test) and confirmed the following cases > work as expected. > > 1) Charset conversion under locale other than UTF-8. > 2) putclip error. > 3) 32-bit and 64-bit inter-operability. One small thing I noticed is that time stamp of /dev/clipboard is broken with the following scenario. 1) Run 'echo A | putclip' in 32bit cygwin 2) Run 'ls -l /dev/clipboard' in 64bit cygwin -- 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: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test)
On 2021-11-04 02:47, Mark Geisert wrote: Hi Thomas, Thomas Wolff wrote: Am 04.11.2021 um 05:31 schrieb Mark Geisert: Takashi Yano via Cygwin wrote: On Wed, 3 Nov 2021 02:59:38 -0700 Mark Geisert wrote: The following packages have been uploaded to the Cygwin distribution: * cygutils-1.4.16-8 * cygutils-extra-1.4.16-8 * cygutils-x11-1.4.16-8 I have tested the 1.4.16-8 (Test) and confirmed the following cases work as expected. 1) Charset conversion under locale other than UTF-8. 2) putclip error. 3) 32-bit and 64-bit inter-operability. I was trying to check changes, and clipboard handling, but the contents of the source packages is identical; files are from 2017‽ Yes, an artifact of how Charles (original author) set up package builds. One has to do a 'cygport cygutils.cygport prep' step to apply patches to get the most up-to-date source. $ cygport cygutils.cygport get prep # [nit] it's also checked in to cygwin-apps: https://cygwin.com/git/?p=cygwin-apps/cygutils.git;a=commitdiff -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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: C standard library: standard headers may reserve non-standard identifiers which don't begin with an underscore
On 2021-11-04 06:40, Corinna Vinschen via Cygwin wrote:
On Nov 4 00:23, Pavel M via Cygwin wrote:
Observation: C standard library: standard headers may reserve non-standard
identifiers which don't begin with an underscore.
Invocations:
$ echo -e "#include \n#define NL_NMAX" | gcc -xc - -std=c11
-pedantic -Wall -Wextra -E > /dev/null
:2: warning: "NL_NMAX" redefined
In file included from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:203,
from
/usr/lib/gcc/x86_64-pc-cygwin/11/include/syslimits.h:7,
from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:34,
from :1:
/usr/include/limits.h:507: note: this is the location of the previous
definition
507 | #define NL_NMAX INT_MAX
$ echo -e "#include \n#define PAGESIZE" | gcc -xc - -std=c11
-pedantic -Wall -Wextra -E > /dev/null
:2: warning: "PAGESIZE" redefined
In file included from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:203,
from
/usr/lib/gcc/x86_64-pc-cygwin/11/include/syslimits.h:7,
from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:34,
from :1:
/usr/include/limits.h:220: note: this is the location of the previous
definition
220 | #define PAGESIZE __PAGESIZE
# and so on...
That's ok for limits.h, see
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
Some of the values also use feature test macros.
Most Unix implementations follow POSIX over C and those compilers
default to POSIX and/or GNU over strict C standards.
As they use feature test macros, most/all of these should be suppressed
if your compiler supports -stdXX or equivalent and issue standard
required diagnostics with -pedantic{,-errors} or equivalent.
Library interfaces may also provide means to prefer certain standard
calling sequences over de facto alternatives.
See your compiler and library newlib/libc documentation under Standards
or equivalent e.g
$ info gcc Standards
$ info libc Standards
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
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: Request for updates to packages itcl 4.1.1, itk 4.1.0, iwidgets 4.1.1
Op vr 29 okt. 2021 om 17:13 schreef Claudius Schnörr: > if cygwin was updated to these package versions: itcl 4.1.1, itk 4.1.0, > iwidgets 4.1.1 > the package git://sourceware.org/git/insight.git, a very good > GUI-frontend to gdb, would be available on cygwin again. > > Attached are the cygport files with necessary modifications the > maintainer of insight provided. These are no patches but might be > helpful for cygwin packagers by comparing them to the original ones. > > When upgrades to these packages are available I can check whether > insight can be built on cygwin. Thank you for your interest. Itcl/Itk 4.2.2 is close to being released, just as Tcl/Tk 8.6.12. So you can expect new versions in a few weeks from now. Regards, Jan Nijtmans -- 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
3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
GCM (Git Credential Manager) - Core fails to properly authenticate with previously stored credentials under the latest 3.3.0 release version of the Cygwin DLL (the bug itself and steps to recreate was originally submitted to the GCM-Core team here: https://github.com/microsoft/Git-Credential-Manager-Core/issues/509). By replacing the Cygwin DLL with the 0913 snapshot, the problem no longer occurs. One of the GCM-Core devs suggested it might be a regression issue in the DLL. Unfortunately, I don't have the C chops to explore this further. --Brian -- 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: Confusing Cygwin X / xlaunch issue
On 26/10/2021 16:38, Eliot Moss wrote: On 10/26/2021 4:02 PM, Jon Turney wrote: On 24/10/2021 12:01, Eliot Moss wrote: First, things work fine when I am using just my hi-res laptop display, or that display plus a hi-res external display in "Extend these displays" mode according to Windows 10. At present I am using a lower resolution external display (becaue I am on an extended trip and it's what I have) in "Extend these displays" mode with my hi-res laptop display. This seems to confuse X (and also xlaunch?). Here are the issues: Thanks for reporting this problem. When booted with the external lo-res display as the main display: - xterm windows come up with a very large font. - The X menu (controlled by .XWinrc) does not come up. This means that you're right-clicking on the notification area icon, but no menu appears? Correct. If so, I guess this means that we're getting confused about where to place the menu, but I'm not sure how that could happen. wrt the font scaling issue, looking at the source, it seems that we don't re-consider the display dpi after a WM_DISPLAYCHANGE message, but keep on using the value determined at startup. This is probably a bug. I've made an attempt at fixing this in the xserve 21.1.0-1 test release. The X server should now be aware of Windows DPI changes (only on the primary monitor at the moment), and update the X screen information (and probably emit some kind of xrandr event, which X applications may take note of or not...) (Advertising this awareness also stops Windows from always reporting to it the DPI when it started, and rescaling windows when it changes or they move between monitors with different DPI values (which could lead to some blurriness)) Perhaps you could try that, and see if it improves things for you? -- Jon Turney Volunteer Cygwin/X X Server maintainer -- 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] xorg-server-21.1.0-1 (TEST)
The following packages have been updated in the Cygwin distribution: *** xorg-server-21.1.0-1 *** xorg-server-common-21.1.0-1 *** xorg-server-debuginfo-21.1.0-1 *** xorg-server-devel-21.1.0-1 *** xorg-server-extra-21.1.0-1 *** xorg-server-xorg-21.1.0-1 *** xwinclip-21.1.0-1 These packages contain XWin and the other X.Org X11 servers. This is the first release of the xserver 21.1 series. It is currently available as a test release, and will be made stable in a few weeks, if no major regressions are reported. Please try test releases and report problems to the Cygwin mailing list. Testing helps ensure good releases! In addition to upstream fixes and improvements [1], the following cygwin-specific changes have been made since 1.20.12-1: * In multiwindow mode, remove the X input focus when an X window loses Windows focus (again) Addresses: https://cygwin.com/ml/cygwin/2017-04/msg00168.html * Update X screen DPI when the primary monitor DPI changes (if the '-dpi' option isn't used) Addresses: https://cygwin.com/pipermail/cygwin/2021-October/249687.html * Avoid blurry scaling by DPI value of windows when moving between monitors with different Windows DPI values. * The experimental XWinWMUtil library and headers (only used by the experimental XtoW WM), have been removed Note that the Xdmx server has been removed upstream. [1] https://lists.x.org/archives/xorg-announce/2021-October/003115.html -- 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: C standard library: standard headers may reserve non-standard identifiers which don't begin with an underscore
On Nov 4 00:23, Pavel M via Cygwin wrote: > Observation: C standard library: standard headers may reserve non-standard > identifiers which don't begin with an underscore. > > Invocations: > $ echo -e "#include \n#define NL_NMAX" | gcc -xc - -std=c11 > -pedantic -Wall -Wextra -E > /dev/null > :2: warning: "NL_NMAX" redefined > In file included from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:203, > from > /usr/lib/gcc/x86_64-pc-cygwin/11/include/syslimits.h:7, > from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:34, > from :1: > /usr/include/limits.h:507: note: this is the location of the previous > definition > 507 | #define NL_NMAX INT_MAX > > $ echo -e "#include \n#define PAGESIZE" | gcc -xc - -std=c11 > -pedantic -Wall -Wextra -E > /dev/null > :2: warning: "PAGESIZE" redefined > In file included from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:203, > from > /usr/lib/gcc/x86_64-pc-cygwin/11/include/syslimits.h:7, > from /usr/lib/gcc/x86_64-pc-cygwin/11/include/limits.h:34, > from :1: > /usr/include/limits.h:220: note: this is the location of the previous > definition > 220 | #define PAGESIZE __PAGESIZE > > # and so on... That's ok for limits.h, see https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html Some of the values also use feature test macros. Corinna -- 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] pl 7.6.4-1 (SWI-Prolog)
The following packages have been uploaded to the Cygwin distribution: * pl-7.6.4-1 * pl-devel-7.6.4-1 * pl-doc-7.6.4-1 * pl-odbc-7.6.4-1 * pl-static-7.6.4-1 * pl-xpce-7.6.4-1 This is the last stable release of SWI-Prolog 7.x. While SWI-Prolog moved to 8.x quite some time ago, a change in the build system requires a lot more work, so this 7.6.4 release at least updates the package to openssl 1.1 for the time being. -- 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: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test)
Hi Thomas, Thomas Wolff wrote: Am 04.11.2021 um 05:31 schrieb Mark Geisert: Takashi Yano via Cygwin wrote: On Wed, 3 Nov 2021 02:59:38 -0700 Mark Geisert wrote: The following packages have been uploaded to the Cygwin distribution: * cygutils-1.4.16-8 * cygutils-extra-1.4.16-8 * cygutils-x11-1.4.16-8 [...] I have tested the 1.4.16-8 (Test) and confirmed the following cases work as expected. 1) Charset conversion under locale other than UTF-8. 2) putclip error. 3) 32-bit and 64-bit inter-operability. I was trying to check changes, and clipboard handling, but the contents of the source packages is identical; files are from 2017‽ Yes, an artifact of how Charles (original author) set up package builds. One has to do a 'cygport cygutils.cygport prep' step to apply patches to get the most up-to-date source. ..mark -- 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
