Please update qt5 package
Cygwin is stuck at qt5.9. Many projects now requires at least qt5.12 and recommended qt5.15. Also please package qtwebengine and possibly qtwebkit, too. Thanks. Sent with ProtonMail Secure Email. -- 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: sed 4.8
The following packages have been upgraded in the Cygwin distribution: * sed 4.8 The sed (Stream EDitor) editor is a stream or batch (non-interactive) editor. Sed takes text as input, performs an operation or set of operations on the text, and outputs the modified text. The operations that sed performs (substitutions, deletions, insertions, etc.) can be specified in a script file or from the command line. For more information see the project home pages: https://www.gnu.org/software/sed/ https://sv.gnu.org/projects/sed/ For changes since the previous Cygwin release please see below or read /usr/share/doc/sed/NEWS after installation; for complete details see: /usr/share/doc/sed/ChangeLog https://git.sv.gnu.org/gitweb/?p=sed.git;a=log;h=refs/tags/v4.8 Noteworthy changes in release 4.8 (2020-01-14) [stable] * Bug fixes "sed -i" now creates temporary files with correct umask (limited to u=rwx). Previously sed would incorrectly set umask on temporary files, resulting in problems under certain fuse-like file systems. [bug introduced in sed 4.2.1] * Release distribute gzip-compressed tarballs once again * Improvements a year's worth of gnulib development, including improved DFA performance Noteworthy changes in release 4.7 (2018-12-20) [stable] * Bug fixes Some uses of \b in the C locale and with the DFA matcher would fail, e.g., the following would mistakenly print "123-x" instead of "123": echo 123-x|LC_ALL=C sed 's/.\bx//' Using a multibyte locale or certain regexp constructs (some ranges, backreferences) would avoid the bug. [bug introduced in sed 4.6] Noteworthy changes in release 4.6 (2018-12-19) [stable] * Improvements sed now prints a clear error message when r/R/w/W (and s///w) commands are missing a filename. Previously, w/W commands would fail with confusing error message, while r/R would be a silent no-op. sed now uses fully-buffered output (instead of line-buffered) when writing to files. This should noticeably improve performance of "sed -i" and other write commands. Buffering can be disabled (as before) with "sed -u". sed in non-cygwin windows environments (e.g. mingw) now properly handles '\n' newlines in -b/--binary mode. * Bug fixes sed no longer accesses invalid memory (heap overflow) when given invalid backreferences in 's' command [bug#32082, present at least since sed-4.0.6]. sed no longer adds extraneous NUL when given s/$//n command. [related to bug#32271, present since sed-4.0.7] sed no longer accesses invalid memory (heap overflow) with s/$//n regexes. [bug#32271, present since sed-4.3]. * New Features New option, --debug: print the input sed script in canonical form and annotate program execution. Noteworthy changes in release 4.5 (2018-03-31) [stable] * Bug fixes sed now fails when matching very long input lines (>2GB). Before, sed would silently ignore the regex without indicating an error. [Bug present at least since sed-3.02] sed no longer rejects comments and closing braces after y/// commands. [Bug existed at least since sed-3.02] sed -E --posix no longer ignores special meaning of '+','?','|' . [Bug introduced in the original implementation of --posix option in v4.1a-5-gba68fb4] sed -i now creates selinux context based on the context of the symlink instead of the symlink target. [Bug present since at least sed-4.2] sed -i --follow-symlinks remains unchanged. sed now treats the sequence '\x5c' (ASCII 92, backslash) as literal backslash character, not as an escape prefix character. [Bug present since sed-3.02.80] Old behavior: $ echo z | sed -E 's/(z)/\x5c1/' # identical to 's/(z)/\1/' z New behavior: $ echo z | sed -E 's/(z)/\x5c1/' \1 -- 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: sed 4.8
The following packages have been upgraded in the Cygwin distribution: * sed 4.8 The sed (Stream EDitor) editor is a stream or batch (non-interactive) editor. Sed takes text as input, performs an operation or set of operations on the text, and outputs the modified text. The operations that sed performs (substitutions, deletions, insertions, etc.) can be specified in a script file or from the command line. For more information see the project home pages: https://www.gnu.org/software/sed/ https://sv.gnu.org/projects/sed/ For changes since the previous Cygwin release please see below or read /usr/share/doc/sed/NEWS after installation; for complete details see: /usr/share/doc/sed/ChangeLog https://git.sv.gnu.org/gitweb/?p=sed.git;a=log;h=refs/tags/v4.8 Noteworthy changes in release 4.8 (2020-01-14) [stable] * Bug fixes "sed -i" now creates temporary files with correct umask (limited to u=rwx). Previously sed would incorrectly set umask on temporary files, resulting in problems under certain fuse-like file systems. [bug introduced in sed 4.2.1] * Release distribute gzip-compressed tarballs once again * Improvements a year's worth of gnulib development, including improved DFA performance Noteworthy changes in release 4.7 (2018-12-20) [stable] * Bug fixes Some uses of \b in the C locale and with the DFA matcher would fail, e.g., the following would mistakenly print "123-x" instead of "123": echo 123-x|LC_ALL=C sed 's/.\bx//' Using a multibyte locale or certain regexp constructs (some ranges, backreferences) would avoid the bug. [bug introduced in sed 4.6] Noteworthy changes in release 4.6 (2018-12-19) [stable] * Improvements sed now prints a clear error message when r/R/w/W (and s///w) commands are missing a filename. Previously, w/W commands would fail with confusing error message, while r/R would be a silent no-op. sed now uses fully-buffered output (instead of line-buffered) when writing to files. This should noticeably improve performance of "sed -i" and other write commands. Buffering can be disabled (as before) with "sed -u". sed in non-cygwin windows environments (e.g. mingw) now properly handles '\n' newlines in -b/--binary mode. * Bug fixes sed no longer accesses invalid memory (heap overflow) when given invalid backreferences in 's' command [bug#32082, present at least since sed-4.0.6]. sed no longer adds extraneous NUL when given s/$//n command. [related to bug#32271, present since sed-4.0.7] sed no longer accesses invalid memory (heap overflow) with s/$//n regexes. [bug#32271, present since sed-4.3]. * New Features New option, --debug: print the input sed script in canonical form and annotate program execution. Noteworthy changes in release 4.5 (2018-03-31) [stable] * Bug fixes sed now fails when matching very long input lines (>2GB). Before, sed would silently ignore the regex without indicating an error. [Bug present at least since sed-3.02] sed no longer rejects comments and closing braces after y/// commands. [Bug existed at least since sed-3.02] sed -E --posix no longer ignores special meaning of '+','?','|' . [Bug introduced in the original implementation of --posix option in v4.1a-5-gba68fb4] sed -i now creates selinux context based on the context of the symlink instead of the symlink target. [Bug present since at least sed-4.2] sed -i --follow-symlinks remains unchanged. sed now treats the sequence '\x5c' (ASCII 92, backslash) as literal backslash character, not as an escape prefix character. [Bug present since sed-3.02.80] Old behavior: $ echo z | sed -E 's/(z)/\x5c1/' # identical to 's/(z)/\1/' z New behavior: $ echo z | sed -E 's/(z)/\x5c1/' \1
[ANNOUNCEMENT] Updated: m4 1.4.19
The following packages have been upgraded in the Cygwin distribution: * m41.4.19 An implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example, handling more than 9 positional parameters to macros). GNU m4 also has built-in functions for including files, running shell commands, doing arithmetic, etc. For more information see the project home pages: https://www.gnu.org/software/m4/ https://sv.gnu.org/projects/m4/ For changes since the previous Cygwin release please see below or read /usr/share/doc/m4/NEWS after installation; for complete details see: /usr/share/doc/m4/ChangeLog https://git.sv.gnu.org/gitweb/?p=m4.git;a=log;h=refs/tags/v1.4.19 Noteworthy changes in release 1.4.19 (2021-05-28) [stable] * A number of portability improvements inherited from gnulib, including the ability to perform stack overflow detection on more platforms without linking to GNU libsigsegv. Noteworthy changes in release 1.4.18d (2021-05-11) [beta] * A number of portability improvements inherited from gnulib. Noteworthy changes in release 1.4.18b (2021-05-07) [beta] * The symbol hash table now defaults to 65537 buckets instead of 509, as modern systems have enough memory to benefit from fewer hash collisions by default. * Introduce the use of gettext, with the immediate benefit of nicer UTF-8 author names. Over time, more translations of program messages will become available. * A number of portability improvements inherited from gnulib. -- 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: bison 3.7.6
The following packages have been upgraded in the Cygwin distribution: * bison 3.7.6 Bison is a general-purpose parser generator that converts an annotated context-free grammar into a deterministic LR or generalized LR (GLR) parser employing LALR(1) parser tables. As an experimental feature, Bison can also generate IELR(1) or canonical LR(1) parser tables. Once you are proficient with Bison, you can use it to develop a wide range of language parsers, from those used in simple desk calculators to complex programming languages. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble. You need to be fluent in C or C++ programming in order to use Bison. Java is also supported as an experimental feature. For more information see the project home pages: https://www.gnu.org/software/bison/ https://sv.gnu.org/projects/bison/ As there have been many changes since the previous Cygwin release please see below or read /usr/share/doc/bison/NEWS after installation; for complete details see: /usr/share/doc/bison/ChangeLog https://git.sv.gnu.org/gitweb/?p=bison.git;a=log;h=refs/tags/v3.7.6 Noteworthy changes in release 3.7.6 (2021-03-08) [stable] * Bug fixes - Reused Push Parsers When a push-parser state structure is used for multiple parses, it was possible for some state to leak from one run into the following one. - Fix Table Generation In some very rare conditions, when there are many useless tokens, it was possible to generate incorrect parsers. Noteworthy changes in release 3.7.5 (2021-01-24) [stable] * Bug fixes - Counterexample Generation In some cases counterexample generation could crash. This is fixed. - Fix Table Generation In some very rare conditions, when there are many useless tokens, it was possible to generate incorrect parsers. - GLR parsers now support %merge together with api.value.type=union. - C++ parsers use noexcept in more places. - Generated parsers avoid some warnings about signedness issues. - C-language parsers now avoid warnings from pedantic clang. - C-language parsers now work around quirks of HP-UX 11.23 (2003). Noteworthy changes in release 3.7.4 (2020-11-14) [stable] * Bug fixes - Bug fixes in yacc.c In Yacc mode, all the tokens are defined twice: once as an enum, and then as a macro. YYEMPTY was missing its macro. - Bug fixes in lalr1.cc The lalr1.cc skeleton used to emit internal assertions (using YY_ASSERT) even when the `parse.assert` %define variable is not enabled. It no longer does. The private internal macro YY_ASSERT now obeys the `api.prefix` %define variable. When there is a very large number of tokens, some assertions could be long enough to hit arbitrary limits in Visual C++. They have been rewritten to work around this limitation. * Changes The YYBISON macro in generated "regular C parsers" (from the "yacc.c" skeleton) used to be defined to 1. It is now defined to the version of Bison as an integer (e.g., 30704 for version 3.7.4). Noteworthy changes in release 3.7.3 (2020-10-13) [stable] * Bug fixes Fix concurrent build issues. The bison executable is no longer linked uselessly against libreadline. Fix incorrect use of yytname in glr.cc. Noteworthy changes in release 3.7.2 (2020-09-05) [stable] This release of Bison fixes all known bugs reported for Bison in MITRE's Common Vulnerabilities and Exposures (CVE) system. These vulnerabilities are only about bison-the-program itself, not the generated code. Although these bugs are typically irrelevant to how Bison is used, they are worth fixing if only to give users peace of mind. There is no known vulnerability in the generated parsers. * Bug fixes Fix concurrent build issues (introduced in Bison 3.5). Push parsers always use YYMALLOC/YYFREE (no direct calls to malloc/free). Fix portability issues of the test suite, and of bison itself. Some unlikely crashes found by fuzzing have been fixed. This is only about bison itself, not the generated parsers. Noteworthy changes in release 3.7.1 (2020-08-02) [stable] * Bug fixes Crash when a token alias contains a NUL byte. Portability issues with libtextstyle. Portability issues of Bison itself with MSVC. * Changes Improvements and fixes in the documentation. More precise location about symbol type redefinitions. Noteworthy changes in release 3.7 (2020-07-23) [stable] * Deprecated features The YYPRINT macro, which works only with yacc.c and only for tokens, was obsoleted long ago by %printer, introduced in Bison 1.50 (November 2002). It is deprecated and its support will be removed eventually. In conformance with the recommendations of the Graphviz team, in the next version Bison the option `--graph` will generate a *.gv file by default, instead of *.dot. A transition
Updated: m4 1.4.19
The following packages have been upgraded in the Cygwin distribution: * m41.4.19 An implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example, handling more than 9 positional parameters to macros). GNU m4 also has built-in functions for including files, running shell commands, doing arithmetic, etc. For more information see the project home pages: https://www.gnu.org/software/m4/ https://sv.gnu.org/projects/m4/ For changes since the previous Cygwin release please see below or read /usr/share/doc/m4/NEWS after installation; for complete details see: /usr/share/doc/m4/ChangeLog https://git.sv.gnu.org/gitweb/?p=m4.git;a=log;h=refs/tags/v1.4.19 Noteworthy changes in release 1.4.19 (2021-05-28) [stable] * A number of portability improvements inherited from gnulib, including the ability to perform stack overflow detection on more platforms without linking to GNU libsigsegv. Noteworthy changes in release 1.4.18d (2021-05-11) [beta] * A number of portability improvements inherited from gnulib. Noteworthy changes in release 1.4.18b (2021-05-07) [beta] * The symbol hash table now defaults to 65537 buckets instead of 509, as modern systems have enough memory to benefit from fewer hash collisions by default. * Introduce the use of gettext, with the immediate benefit of nicer UTF-8 author names. Over time, more translations of program messages will become available. * A number of portability improvements inherited from gnulib.
Updated: bison 3.7.6
The following packages have been upgraded in the Cygwin distribution: * bison 3.7.6 Bison is a general-purpose parser generator that converts an annotated context-free grammar into a deterministic LR or generalized LR (GLR) parser employing LALR(1) parser tables. As an experimental feature, Bison can also generate IELR(1) or canonical LR(1) parser tables. Once you are proficient with Bison, you can use it to develop a wide range of language parsers, from those used in simple desk calculators to complex programming languages. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble. You need to be fluent in C or C++ programming in order to use Bison. Java is also supported as an experimental feature. For more information see the project home pages: https://www.gnu.org/software/bison/ https://sv.gnu.org/projects/bison/ As there have been many changes since the previous Cygwin release please see below or read /usr/share/doc/bison/NEWS after installation; for complete details see: /usr/share/doc/bison/ChangeLog https://git.sv.gnu.org/gitweb/?p=bison.git;a=log;h=refs/tags/v3.7.6 Noteworthy changes in release 3.7.6 (2021-03-08) [stable] * Bug fixes - Reused Push Parsers When a push-parser state structure is used for multiple parses, it was possible for some state to leak from one run into the following one. - Fix Table Generation In some very rare conditions, when there are many useless tokens, it was possible to generate incorrect parsers. Noteworthy changes in release 3.7.5 (2021-01-24) [stable] * Bug fixes - Counterexample Generation In some cases counterexample generation could crash. This is fixed. - Fix Table Generation In some very rare conditions, when there are many useless tokens, it was possible to generate incorrect parsers. - GLR parsers now support %merge together with api.value.type=union. - C++ parsers use noexcept in more places. - Generated parsers avoid some warnings about signedness issues. - C-language parsers now avoid warnings from pedantic clang. - C-language parsers now work around quirks of HP-UX 11.23 (2003). Noteworthy changes in release 3.7.4 (2020-11-14) [stable] * Bug fixes - Bug fixes in yacc.c In Yacc mode, all the tokens are defined twice: once as an enum, and then as a macro. YYEMPTY was missing its macro. - Bug fixes in lalr1.cc The lalr1.cc skeleton used to emit internal assertions (using YY_ASSERT) even when the `parse.assert` %define variable is not enabled. It no longer does. The private internal macro YY_ASSERT now obeys the `api.prefix` %define variable. When there is a very large number of tokens, some assertions could be long enough to hit arbitrary limits in Visual C++. They have been rewritten to work around this limitation. * Changes The YYBISON macro in generated "regular C parsers" (from the "yacc.c" skeleton) used to be defined to 1. It is now defined to the version of Bison as an integer (e.g., 30704 for version 3.7.4). Noteworthy changes in release 3.7.3 (2020-10-13) [stable] * Bug fixes Fix concurrent build issues. The bison executable is no longer linked uselessly against libreadline. Fix incorrect use of yytname in glr.cc. Noteworthy changes in release 3.7.2 (2020-09-05) [stable] This release of Bison fixes all known bugs reported for Bison in MITRE's Common Vulnerabilities and Exposures (CVE) system. These vulnerabilities are only about bison-the-program itself, not the generated code. Although these bugs are typically irrelevant to how Bison is used, they are worth fixing if only to give users peace of mind. There is no known vulnerability in the generated parsers. * Bug fixes Fix concurrent build issues (introduced in Bison 3.5). Push parsers always use YYMALLOC/YYFREE (no direct calls to malloc/free). Fix portability issues of the test suite, and of bison itself. Some unlikely crashes found by fuzzing have been fixed. This is only about bison itself, not the generated parsers. Noteworthy changes in release 3.7.1 (2020-08-02) [stable] * Bug fixes Crash when a token alias contains a NUL byte. Portability issues with libtextstyle. Portability issues of Bison itself with MSVC. * Changes Improvements and fixes in the documentation. More precise location about symbol type redefinitions. Noteworthy changes in release 3.7 (2020-07-23) [stable] * Deprecated features The YYPRINT macro, which works only with yacc.c and only for tokens, was obsoleted long ago by %printer, introduced in Bison 1.50 (November 2002). It is deprecated and its support will be removed eventually. In conformance with the recommendations of the Graphviz team, in the next version Bison the option `--graph` will generate a *.gv file by default, instead of *.dot. A transition
[ANNOUNCEMENT] Test: libreadline{7,-devel} 8.1 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * libreadline7 8.1 * libreadline-devel 8.1 The readline library will read a line from the terminal and return it, allowing the user to edit the line with the standard emacs editing keys. It allows the programmer to give the user an easier-to-use and more intuitive interface. Please test this Base category library as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: http://tiswww.cwru.edu/php/chet/readline/rltop.html https://sv.gnu.org/projects/readline/ For changes since the previous Cygwin release please see below or read /usr/share/doc/readline/NEWS after installation: https://git.sv.gnu.org/gitweb/?p=readline.git;f=NEWS;hb=readline-8.1 New features added to readline-8.1 a. If a second consecutive completion attempt produces matches where the first did not, treat it as a new completion attempt and insert a match as appropriate. b. Bracketed paste mode works in more places: incremental search strings, vi overstrike mode, character search, and reading numeric arguments. c. Readline automatically switches to horizontal scrolling if the terminal has only one line. d. Unbinding all key sequences bound to a particular readline function now descends into keymaps for multi-key sequences. e. rl-clear-display: new bindable command that clears the screen and, if possible, the scrollback buffer (bound to emacs mode M-C-l by default). f. New active mark and face feature: when enabled, it will highlight the text inserted by a bracketed paste (the `active region') and the text found by incremental and non-incremental history searches. This is tied to bracketed paste and can be disabled by turning off bracketed paste. g. Readline sets the mark in several additional commands. h. Bracketed paste mode is enabled by default. There is a configure-time option (--enable-bracketed-paste-default) to set the default to on or off. i. Readline tries to take advantage of the more regular structure of UTF-8 characters to identify the beginning and end of characters when moving through the line buffer. j. The bindable operate-and-get-next command (and its default bindings) are now part of readline instead of a bash-specific addition. k. The signal cleanup code now blocks SIGINT while processing after a SIGINT. New features added to readline-8.0 a. Non-incremental vi-mode search (`N', `n') can search for a shell pattern, as Posix specifies (uses fnmatch(3) if available). b. There are new `next-screen-line' and `previous-screen-line' bindable commands, which move the cursor to the same column in the next, or previous, physical line, respectively. c. There are default key bindings for control-arrow-key key combinations. d. A negative argument (-N) to `quoted-insert' means to insert the next N characters using quoted-insert. e. New public function: rl_check_signals(), which allows applications to respond to signals that readline catches while waiting for input using a custom read function. f. There is new support for conditionally testing the readline version in an inputrc file, with a full set of arithmetic comparison operators available. g. There is a simple variable comparison facility available for use within an inputrc file. Allowable operators are equality and inequality; string variables may be compared to a value; boolean variables must be compared to either `on' or `off'; variable names are separated from the operator by whitespace. h. The history expansion library now understands command and process substitution and extended globbing and allows them to appear anywhere in a word. i. The history library has a new variable that allows applications to set the initial quoting state, so quoting state can be inherited from a previous line. j. Readline now allows application-defined keymap names; there is a new public function, rl_set_keymap_name(), to do that. k. The "Insert" keypad key, if available, now puts readline into overwrite mode. -- 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
Test: libreadline{7,-devel} 8.1 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * libreadline7 8.1 * libreadline-devel 8.1 The readline library will read a line from the terminal and return it, allowing the user to edit the line with the standard emacs editing keys. It allows the programmer to give the user an easier-to-use and more intuitive interface. Please test this Base category library as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: http://tiswww.cwru.edu/php/chet/readline/rltop.html https://sv.gnu.org/projects/readline/ For changes since the previous Cygwin release please see below or read /usr/share/doc/readline/NEWS after installation: https://git.sv.gnu.org/gitweb/?p=readline.git;f=NEWS;hb=readline-8.1 New features added to readline-8.1 a. If a second consecutive completion attempt produces matches where the first did not, treat it as a new completion attempt and insert a match as appropriate. b. Bracketed paste mode works in more places: incremental search strings, vi overstrike mode, character search, and reading numeric arguments. c. Readline automatically switches to horizontal scrolling if the terminal has only one line. d. Unbinding all key sequences bound to a particular readline function now descends into keymaps for multi-key sequences. e. rl-clear-display: new bindable command that clears the screen and, if possible, the scrollback buffer (bound to emacs mode M-C-l by default). f. New active mark and face feature: when enabled, it will highlight the text inserted by a bracketed paste (the `active region') and the text found by incremental and non-incremental history searches. This is tied to bracketed paste and can be disabled by turning off bracketed paste. g. Readline sets the mark in several additional commands. h. Bracketed paste mode is enabled by default. There is a configure-time option (--enable-bracketed-paste-default) to set the default to on or off. i. Readline tries to take advantage of the more regular structure of UTF-8 characters to identify the beginning and end of characters when moving through the line buffer. j. The bindable operate-and-get-next command (and its default bindings) are now part of readline instead of a bash-specific addition. k. The signal cleanup code now blocks SIGINT while processing after a SIGINT. New features added to readline-8.0 a. Non-incremental vi-mode search (`N', `n') can search for a shell pattern, as Posix specifies (uses fnmatch(3) if available). b. There are new `next-screen-line' and `previous-screen-line' bindable commands, which move the cursor to the same column in the next, or previous, physical line, respectively. c. There are default key bindings for control-arrow-key key combinations. d. A negative argument (-N) to `quoted-insert' means to insert the next N characters using quoted-insert. e. New public function: rl_check_signals(), which allows applications to respond to signals that readline catches while waiting for input using a custom read function. f. There is new support for conditionally testing the readline version in an inputrc file, with a full set of arithmetic comparison operators available. g. There is a simple variable comparison facility available for use within an inputrc file. Allowable operators are equality and inequality; string variables may be compared to a value; boolean variables must be compared to either `on' or `off'; variable names are separated from the operator by whitespace. h. The history expansion library now understands command and process substitution and extended globbing and allows them to appear anywhere in a word. i. The history library has a new variable that allows applications to set the initial quoting state, so quoting state can be inherited from a previous line. j. Readline now allows application-defined keymap names; there is a new public function, rl_set_keymap_name(), to do that. k. The "Insert" keypad key, if available, now puts readline into overwrite mode.
[ANNOUNCEMENT] Test: gzip 1.10 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * gzip 1.10 GNU Gzip is a popular data compression program originally written by Jean-Loup Gailly for the GNU project. Mark Adler wrote the decompression part. It was developed as a replacement for compress because of Unisys and IBM patents covering the LZW algorithm at the time. The superior compression ratio of gzip is just a bonus. Please test this Base category utility as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, scripts, cron jobs, and cygport builds, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: https://www.gnu.org/software/gzip/ https://sv.gnu.org/projects/gzip/ For changes since the previous Cygwin release please see below or read /usr/share/doc/gzip/NEWS after installation; for complete details see: /usr/share/doc/gzip/ChangeLog https://git.sv.gnu.org/gitweb/?p=gzip.git;a=log;h=refs/tags/v1.10 Noteworthy changes in release 1.10 (2018-12-29) [stable] * Changes in behavior Compressed gzip output no longer contains the current time as a timestamp when the input is not a regular file. Instead, the output contains a null (zero) timestamp. This makes gzip's behavior more reproducible when used as part of a pipeline. (As a reminder, even regular files will use null timestamps after the year 2106, due to a limitation in the gzip format.) * Bug fixes A use of uninitialized memory on some malformed inputs has been fixed. [bug present since the beginning] A few theoretical race conditions in signal handers have been fixed. These bugs most likely do not happen on practical platforms. [bugs present since the beginning] Noteworthy changes in release 1.9 (2018-01-07) [stable] * Bug fixes gzip -d -S SUFFIX file.SUFFIX would fail for any upper-case byte in SUFFIX. E.g., before, this command would fail: $ :|gzip > kT && gzip -d -S T kT gzip: kT: unknown suffix -- ignored [bug present since the beginning] When decompressing data in 'pack' format, gzip no longer mishandles leading zeros in the end-of-block code. [bug introduced in gzip-1.6] When converting from system-dependent time_t format to the 32-bit unsigned MTIME format used in gzip files, if a timestamp does not fit gzip now substitutes zero instead of the timestamp's low-order 32 bits, as per Internet RFC 1952. When converting from MTIME to time_t format, if a timestamp does not fit gzip now warns and substitutes the nearest in-range value instead of crashing or silently substituting an implementation-defined value (typically, the timestamp's low-order bits). This affects timestamps before 1970 and after 2106, and timestamps after 2038 on platforms with 32-bit signed time_t. [bug present since the beginning] Commands implemented via shell scripts are now more consistent about failure status. For example, 'gunzip --help >/dev/full' now consistently exits with status 1 (error), instead of with status 2 (warning) on some platforms. [bug present since the beginning] Support for VMS and Amiga has been removed. It was not working anyway, and it reportedly caused file name glitches on MS-Windowsish platforms. -- 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
Test: gzip 1.10 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * gzip 1.10 GNU Gzip is a popular data compression program originally written by Jean-Loup Gailly for the GNU project. Mark Adler wrote the decompression part. It was developed as a replacement for compress because of Unisys and IBM patents covering the LZW algorithm at the time. The superior compression ratio of gzip is just a bonus. Please test this Base category utility as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, scripts, cron jobs, and cygport builds, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: https://www.gnu.org/software/gzip/ https://sv.gnu.org/projects/gzip/ For changes since the previous Cygwin release please see below or read /usr/share/doc/gzip/NEWS after installation; for complete details see: /usr/share/doc/gzip/ChangeLog https://git.sv.gnu.org/gitweb/?p=gzip.git;a=log;h=refs/tags/v1.10 Noteworthy changes in release 1.10 (2018-12-29) [stable] * Changes in behavior Compressed gzip output no longer contains the current time as a timestamp when the input is not a regular file. Instead, the output contains a null (zero) timestamp. This makes gzip's behavior more reproducible when used as part of a pipeline. (As a reminder, even regular files will use null timestamps after the year 2106, due to a limitation in the gzip format.) * Bug fixes A use of uninitialized memory on some malformed inputs has been fixed. [bug present since the beginning] A few theoretical race conditions in signal handers have been fixed. These bugs most likely do not happen on practical platforms. [bugs present since the beginning] Noteworthy changes in release 1.9 (2018-01-07) [stable] * Bug fixes gzip -d -S SUFFIX file.SUFFIX would fail for any upper-case byte in SUFFIX. E.g., before, this command would fail: $ :|gzip > kT && gzip -d -S T kT gzip: kT: unknown suffix -- ignored [bug present since the beginning] When decompressing data in 'pack' format, gzip no longer mishandles leading zeros in the end-of-block code. [bug introduced in gzip-1.6] When converting from system-dependent time_t format to the 32-bit unsigned MTIME format used in gzip files, if a timestamp does not fit gzip now substitutes zero instead of the timestamp's low-order 32 bits, as per Internet RFC 1952. When converting from MTIME to time_t format, if a timestamp does not fit gzip now warns and substitutes the nearest in-range value instead of crashing or silently substituting an implementation-defined value (typically, the timestamp's low-order bits). This affects timestamps before 1970 and after 2106, and timestamps after 2038 on platforms with 32-bit signed time_t. [bug present since the beginning] Commands implemented via shell scripts are now more consistent about failure status. For example, 'gunzip --help >/dev/full' now consistently exits with status 1 (error), instead of with status 2 (warning) on some platforms. [bug present since the beginning] Support for VMS and Amiga has been removed. It was not working anyway, and it reportedly caused file name glitches on MS-Windowsish platforms.
[ANNOUNCEMENT] Test: grep 3.6 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * grep 3.6 GNU grep searches one or more input files for lines containing a match to a specified pattern. By default, grep outputs the matching lines. The GNU implementation includes several useful extensions over POSIX. Please test this Base category utility as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, scripts, cron jobs, and cygport builds, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: https://www.gnu.org/software/grep/ https://sv.gnu.org/projects/grep/ For changes since the previous Cygwin release please see below or read /usr/share/doc/grep/NEWS after installation; for complete details see: /usr/share/doc/grep/ChangeLog https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.6 Noteworthy changes in release 3.6 (2020-11-08) [stable] * Changes in behavior The GREP_OPTIONS environment variable no longer affects grep's behavior. The variable was declared obsolescent in grep 2.21 (2014), and since then any use had caused grep to issue a diagnostic. * Bug fixes grep's DFA matcher performed an invalid regex transformation that would convert an ERE like a+a+a+ to a+a+, which would make grep a+a+a+ mistakenly match "aa". [Bug#44351 introduced in grep 3.2] grep -P now reports the troublesome input filename upon PCRE execution failure. Before, searching many files for something rare might fail with just "exceeded PCRE's backtracking limit". Now, it also reports which file triggered the failure. Noteworthy changes in release 3.5 (2020-09-27) [stable] * Changes in behavior The message that a binary file matches is now sent to standard error and the message has been reworded from "Binary file FOO matches" to "grep: FOO: binary file matches", to avoid confusion with ordinary output or when file names contain spaces and the like, and to be more consistent with other diagnostics. For example, commands like 'grep PATTERN FILE | wc' no longer add 1 to the count of matching text lines due to the presence of the message. Like other stderr messages, the message is now omitted if the --no-messages (-s) option is given. Two other stderr messages now use the typical form too. They are now "grep: FOO: warning: recursive directory loop" and "grep: FOO: input file is also the output". The --files-without-match (-L) option has reverted to its behavior in grep 3.1 and earlier. That is, grep -L again succeeds when a line is selected, not when a file is listed. The behavior in grep 3.2 through 3.4 was causing compatibility problems. * Bug fixes grep -I no longer issues a spurious "Binary file FOO matches" line. [Bug#33552 introduced in grep 2.23] In UTF-8 locales, grep -w no longer ignores a multibyte word constituent just before what would otherwise be a word match. [Bug#43225 introduced in grep 2.28] grep -i no longer mishandles ASCII characters that match multibyte characters. For example, 'LC_ALL=tr_TR.utf8 grep -i i' no longer dumps core merely because 'i' matches 'Ä°' (U+0130 LATIN CAPITAL LETTER I WITH DOT ABOVE) in Turkish when ignoring case. [Bug#43577 introduced partly in grep 2.28 and partly in grep 3.4] A performance regression with -E and many patterns has been mostly fixed. "Mostly" as there is a performance tradeoff between Bug#22357 and Bug#40634. [Bug#40634 introduced in grep 2.28] A performance regression with many duplicate patterns has been fixed. [Bug#43040 introduced in grep 3.4] An N^2 RSS performance regression with many patterns has been fixed in common cases (no backref, and no use of -o or --color). With only 80,000 lines of /usr/share/dict/linux.words, the following would use 100GB of RSS and take 3 minutes. With the fix, it used less than 400MB and took less than one second: head -8 /usr/share/dict/linux.words > w; grep -vf w w [Bug#43527 introduced in grep 3.4] * Build-related "make dist" builds .tar.gz files again, as they are still used in some barebones builds. Noteworthy changes in release 3.4 (2020-01-02) [stable] * New features The new --no-ignore-case option causes grep to observe case distinctions, overriding any previous -i (--ignore-case) option. * Bug fixes '.' no longer matches some invalid byte sequences in UTF-8 locales. [bug introduced in grep 2.7] grep -Fw can no longer false match in non-UTF-8 multibyte locales For example, this command would erroneously print its input line: echo ab | LC_CTYPE=ja_JP.eucjp grep -Fw b [Bug#38223 introduced in grep 2.28] The
Test: grep 3.6 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * grep 3.6 GNU grep searches one or more input files for lines containing a match to a specified pattern. By default, grep outputs the matching lines. The GNU implementation includes several useful extensions over POSIX. Please test this Base category utility as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed so it is getting used by commands, scripts, cron jobs, and cygport builds, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home pages: https://www.gnu.org/software/grep/ https://sv.gnu.org/projects/grep/ For changes since the previous Cygwin release please see below or read /usr/share/doc/grep/NEWS after installation; for complete details see: /usr/share/doc/grep/ChangeLog https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.6 Noteworthy changes in release 3.6 (2020-11-08) [stable] * Changes in behavior The GREP_OPTIONS environment variable no longer affects grep's behavior. The variable was declared obsolescent in grep 2.21 (2014), and since then any use had caused grep to issue a diagnostic. * Bug fixes grep's DFA matcher performed an invalid regex transformation that would convert an ERE like a+a+a+ to a+a+, which would make grep a+a+a+ mistakenly match "aa". [Bug#44351 introduced in grep 3.2] grep -P now reports the troublesome input filename upon PCRE execution failure. Before, searching many files for something rare might fail with just "exceeded PCRE's backtracking limit". Now, it also reports which file triggered the failure. Noteworthy changes in release 3.5 (2020-09-27) [stable] * Changes in behavior The message that a binary file matches is now sent to standard error and the message has been reworded from "Binary file FOO matches" to "grep: FOO: binary file matches", to avoid confusion with ordinary output or when file names contain spaces and the like, and to be more consistent with other diagnostics. For example, commands like 'grep PATTERN FILE | wc' no longer add 1 to the count of matching text lines due to the presence of the message. Like other stderr messages, the message is now omitted if the --no-messages (-s) option is given. Two other stderr messages now use the typical form too. They are now "grep: FOO: warning: recursive directory loop" and "grep: FOO: input file is also the output". The --files-without-match (-L) option has reverted to its behavior in grep 3.1 and earlier. That is, grep -L again succeeds when a line is selected, not when a file is listed. The behavior in grep 3.2 through 3.4 was causing compatibility problems. * Bug fixes grep -I no longer issues a spurious "Binary file FOO matches" line. [Bug#33552 introduced in grep 2.23] In UTF-8 locales, grep -w no longer ignores a multibyte word constituent just before what would otherwise be a word match. [Bug#43225 introduced in grep 2.28] grep -i no longer mishandles ASCII characters that match multibyte characters. For example, 'LC_ALL=tr_TR.utf8 grep -i i' no longer dumps core merely because 'i' matches 'Ä°' (U+0130 LATIN CAPITAL LETTER I WITH DOT ABOVE) in Turkish when ignoring case. [Bug#43577 introduced partly in grep 2.28 and partly in grep 3.4] A performance regression with -E and many patterns has been mostly fixed. "Mostly" as there is a performance tradeoff between Bug#22357 and Bug#40634. [Bug#40634 introduced in grep 2.28] A performance regression with many duplicate patterns has been fixed. [Bug#43040 introduced in grep 3.4] An N^2 RSS performance regression with many patterns has been fixed in common cases (no backref, and no use of -o or --color). With only 80,000 lines of /usr/share/dict/linux.words, the following would use 100GB of RSS and take 3 minutes. With the fix, it used less than 400MB and took less than one second: head -8 /usr/share/dict/linux.words > w; grep -vf w w [Bug#43527 introduced in grep 3.4] * Build-related "make dist" builds .tar.gz files again, as they are still used in some barebones builds. Noteworthy changes in release 3.4 (2020-01-02) [stable] * New features The new --no-ignore-case option causes grep to observe case distinctions, overriding any previous -i (--ignore-case) option. * Bug fixes '.' no longer matches some invalid byte sequences in UTF-8 locales. [bug introduced in grep 2.7] grep -Fw can no longer false match in non-UTF-8 multibyte locales For example, this command would erroneously print its input line: echo ab | LC_CTYPE=ja_JP.eucjp grep -Fw b [Bug#38223 introduced in grep 2.28] The
[ANNOUNCEMENT] Test: dash 0.5.11.4 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * dash 0.5.11.4 DASH is a POSIX-compliant implementation of /bin/sh that aims to be as small as possible. It does this without sacrificing speed where possible. In fact, it is significantly faster than bash (the GNU Bourne-Again SHell) for most tasks. Please test this Base category shell as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed as my /bin/sh so it is used by most scripts, cron jobs, and cygport builds, so it has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home page: http://gondor.apana.org.au/~herbert/dash/ As there have been many changes since the previous Cygwin release please see below; for complete details see: https://git.kernel.org/pub/scm/utils/dash/dash.git/log/?h=v0.5.11.4=1 2021-06-04 Release 0.5.11.4 * eval: Do not cache value of eflag in evaltree 2020-12-23 Release 0.5.11.3 * jobs: Only block in waitcmd on first run 2020-08-28 Release 0.5.11.2 * shell: Group readdir64/dirent64 with open64 2020-07-08 Release 0.5.11.1 * jobs: Fix waitcmd busy loop 2020-06-01 Release 0.5.11 * parser: Fix double-backslash nl in old-style command sub * shell: Fix typos * parser: Save and restore heredoclist in expandstr * shell: Always use explicit large file API * input: Fix compiling against libedit with -fno-common * shell: mktokens relative TMPDIR * expand: Remove unused expandmeta() flag parameter * parser: Fix alias expansion after heredoc or newlines * parser: Catch errors in expandstr * parser: Fix handling of empty aliases * jobs: Fix infinite loop in waitproc * var: Remove poplocalvars() always-zero argument, make it static * jobs: Rename DOWAIT_NORMAL to DOWAIT_NONBLOCK * builtin: Fix seconds part of times(1) * redir: Clear saved redirections in subshell * shell: delete AC_PROG_YACC * parser: Only accept single-digit parameter expansion outside of braces * expand: Fix trailing newlines processing in backquote expanding * parser: Fix old-style command substitution here-document crash * eval: Reset handler when entering a subshell * expand: Fix double-decrement in argstr * options: Do not set commandname in procargs * redir: Handle nested exec within REALLY_CLOSED redirection * output: Fix clang warnings about GNU old-style field designator * shell: Fix clang warnings about "string plus integer" * eval: Only restore exit status on exit/return * eval: avoid leaking memory associated with redirections * system: Disable glibc warning on sigsetmask * eval: Use sh_warnx instead of warnx * parser: Do not push token back before parseheredoc * expand: Eat closing brace for length parameter expansion * eval: Use the correct expansion mode for fd redirection * eval: Silence compiler warning about missing parentheses * shell: Enable automake silent rules * shell: Update configure.ac with suggestions from autoupdate * eval: make traps work when "set -e" is enabled * expand: Fix multiple issues with EXP_DISCARD in evalvar * main: Print \n upon EOF (CTRL-D) when run interactively * eval: Report I/O error on stdout * builtin: Default to mktemp, not tempfile * shell: update .gitignore * man: Problems in dash.1, sh.1, sh.distrib.1 e...@thyrsus.com1 -1/+1 * expand: Ensure result is escaped in cvtnum * memalloc: Avoid looping in growstackto * eval: Always set localvar_stop * expand: Do not reprocess data when expanding words * expand: Fix skipping of command substitution when trimming in evalvar * expand: Merge syntax/quotes in memtodest with flags * expand: Use HOME in tilde expansion when it is empty * shell: Don't include config.h for native helpers * builtin: Use test_access from NetBSD when faccessat is unavailable * eval: Add vfork support * eval: Replace with listsetvar with mklocal/setvareq * eval: Fail immediately with redirections errors for simple command * eval: Add assignment built-in support again * exec: Never rehash regular built-ins * exec: Stricter pathopt parsing * builtin: Mark more regular built-ins * exec: Do not allocate stack string in padvance * memalloc: Add growstackto helper * jobs: Replace some uses of fmtstr with stpcpy/stpncpy * output: Fix fmtstr return value * var: Set IFS to fixed value at start time * parser: Save/restore here-documents in command substitution * jobs: Only clear gotsigchld when waiting for everything * mkinit: Split reset into exitreset and reset * main: Only set savestatus in exitcmd * exec: Return 126 on most errors in shellexec 2018-05-17 Release 0.5.10.2 * parser: Fix incorrect eating of backslash newlines 2018-05-10 Release 0.5.10.1 * jobs - Do not block when waiting on SIGCHLD 2018-05-03 Release 0.5.10 * eval: Variable assignments on
Test: dash 0.5.11.4 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * dash 0.5.11.4 DASH is a POSIX-compliant implementation of /bin/sh that aims to be as small as possible. It does this without sacrificing speed where possible. In fact, it is significantly faster than bash (the GNU Bourne-Again SHell) for most tasks. Please test this Base category shell as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations and has not been upgraded for a few years. I have it locally installed as my /bin/sh so it is used by most scripts, cron jobs, and cygport builds, so it has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a couple of weeks the package will be upgraded to current. For more information see the project home page: http://gondor.apana.org.au/~herbert/dash/ As there have been many changes since the previous Cygwin release please see below; for complete details see: https://git.kernel.org/pub/scm/utils/dash/dash.git/log/?h=v0.5.11.4=1 2021-06-04 Release 0.5.11.4 * eval: Do not cache value of eflag in evaltree 2020-12-23 Release 0.5.11.3 * jobs: Only block in waitcmd on first run 2020-08-28 Release 0.5.11.2 * shell: Group readdir64/dirent64 with open64 2020-07-08 Release 0.5.11.1 * jobs: Fix waitcmd busy loop 2020-06-01 Release 0.5.11 * parser: Fix double-backslash nl in old-style command sub * shell: Fix typos * parser: Save and restore heredoclist in expandstr * shell: Always use explicit large file API * input: Fix compiling against libedit with -fno-common * shell: mktokens relative TMPDIR * expand: Remove unused expandmeta() flag parameter * parser: Fix alias expansion after heredoc or newlines * parser: Catch errors in expandstr * parser: Fix handling of empty aliases * jobs: Fix infinite loop in waitproc * var: Remove poplocalvars() always-zero argument, make it static * jobs: Rename DOWAIT_NORMAL to DOWAIT_NONBLOCK * builtin: Fix seconds part of times(1) * redir: Clear saved redirections in subshell * shell: delete AC_PROG_YACC * parser: Only accept single-digit parameter expansion outside of braces * expand: Fix trailing newlines processing in backquote expanding * parser: Fix old-style command substitution here-document crash * eval: Reset handler when entering a subshell * expand: Fix double-decrement in argstr * options: Do not set commandname in procargs * redir: Handle nested exec within REALLY_CLOSED redirection * output: Fix clang warnings about GNU old-style field designator * shell: Fix clang warnings about "string plus integer" * eval: Only restore exit status on exit/return * eval: avoid leaking memory associated with redirections * system: Disable glibc warning on sigsetmask * eval: Use sh_warnx instead of warnx * parser: Do not push token back before parseheredoc * expand: Eat closing brace for length parameter expansion * eval: Use the correct expansion mode for fd redirection * eval: Silence compiler warning about missing parentheses * shell: Enable automake silent rules * shell: Update configure.ac with suggestions from autoupdate * eval: make traps work when "set -e" is enabled * expand: Fix multiple issues with EXP_DISCARD in evalvar * main: Print \n upon EOF (CTRL-D) when run interactively * eval: Report I/O error on stdout * builtin: Default to mktemp, not tempfile * shell: update .gitignore * man: Problems in dash.1, sh.1, sh.distrib.1 e...@thyrsus.com1 -1/+1 * expand: Ensure result is escaped in cvtnum * memalloc: Avoid looping in growstackto * eval: Always set localvar_stop * expand: Do not reprocess data when expanding words * expand: Fix skipping of command substitution when trimming in evalvar * expand: Merge syntax/quotes in memtodest with flags * expand: Use HOME in tilde expansion when it is empty * shell: Don't include config.h for native helpers * builtin: Use test_access from NetBSD when faccessat is unavailable * eval: Add vfork support * eval: Replace with listsetvar with mklocal/setvareq * eval: Fail immediately with redirections errors for simple command * eval: Add assignment built-in support again * exec: Never rehash regular built-ins * exec: Stricter pathopt parsing * builtin: Mark more regular built-ins * exec: Do not allocate stack string in padvance * memalloc: Add growstackto helper * jobs: Replace some uses of fmtstr with stpcpy/stpncpy * output: Fix fmtstr return value * var: Set IFS to fixed value at start time * parser: Save/restore here-documents in command substitution * jobs: Only clear gotsigchld when waiting for everything * mkinit: Split reset into exitreset and reset * main: Only set savestatus in exitcmd * exec: Return 126 on most errors in shellexec 2018-05-17 Release 0.5.10.2 * parser: Fix incorrect eating of backslash newlines 2018-05-10 Release 0.5.10.1 * jobs - Do not block when waiting on SIGCHLD 2018-05-03 Release 0.5.10 * eval: Variable assignments on
Re: [PATCH] cygutils-extra 1.4.16-3: cygdrop: Fix printf format strings
Christian Franke wrote: This fixes an unrelated bug found during analysis of the cygdrop crash. In theory, the bug affects the 64-bit version (which didn't exist when I contributed this tool in 2009). In practice, it doesn't because 64-bit ABI uses registers to pass the first args of a va_list. Regards, Christian Thank you Christian for the two patches. They'll be part of an upcoming cygutils* 1.4.16-4 release this weekend. ..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
[ANNOUNCEMENT] Updated: fetchmail-6.4.21-1 / fetchmailconf-6.4.21-1
The current upstream release of fetchmail is now available on Cygwin. The upstream release changelog is here: https://sourceforge.net/projects/fetchmail/files/branch_6.4/ This release uses the Python3 interpreter and has been compiled with support for NTLM, GSSAPI authentication, TLSv1.3 is also available. Note This update fixes a regression in the previous release. Kerberos5 support has been removed. This is expected to be the last 6.4.x release for fetchmail, which will be replaced by the 6.5 or 7.x branch releases if and when they become available. -- *** 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: fetchmail-6.4.21-1 / fetchmailconf-6.4.21-1
The current upstream release of fetchmail is now available on Cygwin. The upstream release changelog is here: https://sourceforge.net/projects/fetchmail/files/branch_6.4/ This release uses the Python3 interpreter and has been compiled with support for NTLM, GSSAPI authentication, TLSv1.3 is also available. Note This update fixes a regression in the previous release. Kerberos5 support has been removed. This is expected to be the last 6.4.x release for fetchmail, which will be replaced by the 6.5 or 7.x branch releases if and when they become available. -- *** 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.
Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width
On Fri, 2021-08-13 at 22:37 -0600, Brian Inglis wrote: > On 2021-08-13 22:05, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 23:46:35 -0400 > > > C Linus Hicks wrote: > > > > > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > > > > > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > > > > > On Fri, 13 Aug 2021 21:47:53 -0400 > > > > > > C Linus Hicks wrote: > > > > > > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > > > > > > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > > > > > > > > Works Just Fine For Me! > > > > > > > > > > > > > > > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck > > > > > > > > output attached. > > > > > > > > > > > > > > > > It has been a while since I updated Cygwin; as long as it > > > > > > > > serves my purpose, I generally don't focus > > > > > > > > on that; it is just a tool I use. > > > > > > > > > > > > > > > > Since I did open this thread, of course I need to make sure I > > > > > > > > am up-to-date. I have now done that > > > > > > > > and I don't see issues with Cygwin terminal and less, although > > > > > > > > that is not really where I am > > > > > > > > focusing. I mostly use xterm windows just because there are > > > > > > > > several characteristics I like about it. > > > > > > > > > > > > > > > > I am still seeing issues with xterm and less, as I stated in my > > > > > > > > original post. > > > > > > > > > > > > > > > Did I post this in the wrong list? I have not gotten a response > > > > > > > since my update. > > > > > > > > > > > > 1) Does your problem also happen even if the text file contains only > > > > > > ASCII chars? > > > > > > 2) What does 'which less' say? > > > > > > 3) What does 'infocmp' say? > > > > > > > > > > > > > > > > Most of the files I view have only ASCII text. > > > > > > > > > > lhicks@ESG-Win10-1 ~ > > > > > $ echo $TERM > > > > > xterm > > > > > > > > > > lhicks@ESG-Win10-1 ~ > > > > > $ which less > > > > > /usr/bin/less > > > > > > > > > > lhicks@ESG-Win10-1 ~ > > > > > $ infocmp > > > > > # Reconstructed via infocmp from file: > > > > > /usr/share/terminfo/78/xterm > > > > > > > > > > > > > I should further note that much of the time I am ssh'ed into one of > > > > several different Linux > > > > machines, so in that case, I would be running less from the Linux > > > > machine and displaying in the > > > > Cygwin xterm. > > > > > > > > Hmmm, so now I'm starting to think the combination I have trouble with > > > > is an older less on a Linux > > > > machine and Cygwin xterm. I don't control what is installed on some of > > > > these Linux machines. Do you > > > > know if there were known issues with less, for example, the following > > > > is one that has significant > > > > issues: > > > > > > > > [appldev3@ebs-app-dev3 HAF]$ less --version > > > > less 458 (POSIX regular expressions) > > > > Copyright (C) 1984-2012 Mark Nudelman > > > > > > > > less comes with NO WARRANTY, to the extent permitted by law. > > > > For information about the terms of redistribution, > > > > see the file named README in the less distribution. > > > > Homepage: http://www.greenwoodsoftware.com/less > > > > > > Then, could you please let us know the result of infocmp in the Linux > > > machine you run the less obove in cygwin xterm? > > CentOS 7? xterm 295? ncurses 5.9? > > -- > 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.] > Oracle Linux 7.4 frozen in time. I haven't been able to get them to apply any updates since these machines went into service. XTerm(363) -- from Cygwin ncurses-5.9-13.20130511.el7.x86_64 -- 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: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width
On Sat, 2021-08-14 at 13:35 +0900, Takashi Yano wrote:
> On Sat, 14 Aug 2021 00:05:17 -0400
> C Linus Hicks wrote:
> > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote:
> > > On Fri, 13 Aug 2021 23:46:35 -0400
> > > C Linus Hicks wrote:
> > >
> > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote:
> > > > > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote:
> > > > > > On Fri, 13 Aug 2021 21:47:53 -0400
> > > > > > C Linus Hicks wrote:
> > > > > > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote:
> > > > > > > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote:
> > > > > > > > > Works Just Fine For Me!
> > > > > > > > >
> > > > > > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck
> > > > > > > > output attached.
> > > > > > > >
> > > > > > > > It has been a while since I updated Cygwin; as long as it
> > > > > > > > serves my purpose, I generally don't focus
> > > > > > > > on that; it is just a tool I use.
> > > > > > > >
> > > > > > > > Since I did open this thread, of course I need to make sure I
> > > > > > > > am up-to-date. I have now done that
> > > > > > > > and I don't see issues with Cygwin terminal and less, although
> > > > > > > > that is not really where I am
> > > > > > > > focusing. I mostly use xterm windows just because there are
> > > > > > > > several characteristics I like about it.
> > > > > > > >
> > > > > > > > I am still seeing issues with xterm and less, as I stated in my
> > > > > > > > original post.
> > > > > > > >
> > > > > > > Did I post this in the wrong list? I have not gotten a response
> > > > > > > since my update.
> > > > > >
> > > > > > 1) Does your problem also happen even if the text file contains only
> > > > > >ASCII chars?
> > > > > > 2) What does 'which less' say?
> > > > > > 3) What does 'infocmp' say?
> > > > > >
> > > > >
> > > > > Most of the files I view have only ASCII text.
> > > > >
> > > > > lhicks@ESG-Win10-1 ~
> > > > > $ echo $TERM
> > > > > xterm
> > > > >
> > > > > lhicks@ESG-Win10-1 ~
> > > > > $ which less
> > > > > /usr/bin/less
> > > > >
> > > > > lhicks@ESG-Win10-1 ~
> > > > > $ infocmp
> > > > > # Reconstructed via infocmp from file:
> > > > > /usr/share/terminfo/78/xterm
> > > > >
> > > >
> > > > I should further note that much of the time I am ssh'ed into one of
> > > > several different Linux
> > > > machines, so in that case, I would be running less from the Linux
> > > > machine and displaying in the
> > > > Cygwin xterm.
> > > >
> > > > Hmmm, so now I'm starting to think the combination I have trouble with
> > > > is an older less on a Linux
> > > > machine and Cygwin xterm. I don't control what is installed on some of
> > > > these Linux machines. Do you
> > > > know if there were known issues with less, for example, the following
> > > > is one that has significant
> > > > issues:
> > > >
> > > > [appldev3@ebs-app-dev3 HAF]$ less --version
> > > > less 458 (POSIX regular expressions)
> > > > Copyright (C) 1984-2012 Mark Nudelman
> > > >
> > > > less comes with NO WARRANTY, to the extent permitted by law.
> > > > For information about the terms of redistribution,
> > > > see the file named README in the less distribution.
> > > > Homepage: http://www.greenwoodsoftware.com/less
> > >
> > > Then, could you please let us know the result of infocmp in the Linux
> > > machine you run the less obove in cygwin xterm?
> > >
> >
> > [appldev3@ebs-app-dev3 HAF]$ infocmp
> > # Reconstructed via infocmp from file: /usr/share/terminfo/x/xterm
> > xterm|xterm terminal emulator (X Window System),
> > am, bce, km, mc5i, mir, msgr, npc, xenl,
> > colors#8, cols#80, it#8, lines#24, pairs#64,
> > acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
> > bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
> > clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=^M,
> > csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
> > cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
> > cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
> > cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM,
> > dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K, el1=\E[1K,
> > flash=\E[?5h$<100/>\E[?5l, home=\E[H, hpa=\E[%i%p1%dG,
> > ht=^I, hts=\EH, ich=\E[%p1%d@, il=\E[%p1%dL, il1=\E[L,
> > ind=^J, indn=\E[%p1%dS, invis=\E[8m,
> > is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~, kEND=\E[1;2F,
> > kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D, kNXT=\E[6;2~,
> > kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE, kbs=\177, kcbt=\E[Z,
> > kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
> > kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP, kf10=\E[21~,
> > kf11=\E[23~, kf12=\E[24~, kf13=\E[1;2P, kf14=\E[1;2Q,
> > kf15=\E[1;2R, kf16=\E[1;2S, kf17=\E[15;2~, kf18=\E[17;2~,
> > kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~,
> >
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-DBD-SQLite-1.70-1 perl-Mojolicious-9.21-1 noarch -- perl-HTTP-Tiny-0.078-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-DBD-SQLite-1.70-1 perl-Mojolicious-9.21-1 noarch -- perl-HTTP-Tiny-0.078-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] Re-Release: perl-5.32.1-2 (security)
Perl 5.32.1-2 is now available on Cygwin, replacing perl-5.32.1-1 which has been removed. This is a rebuild of the previous package with one additional patch to fix CVE2021-36770. -- *** 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
Re-Release: perl-5.32.1-2 (security)
Perl 5.32.1-2 is now available on Cygwin, replacing perl-5.32.1-1 which has been removed. This is a rebuild of the previous package with one additional patch to fix CVE2021-36770. -- *** 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.
[PATCH] cygutils-extra 1.4.16-3: cygdrop: Fix printf format strings
This fixes an unrelated bug found during analysis of the cygdrop crash.
In theory, the bug affects the 64-bit version (which didn't exist when I
contributed this tool in 2009).
In practice, it doesn't because 64-bit ABI uses registers to pass the
first args of a va_list.
Regards,
Christian
From 4cf442906ea9654543dd6683960993361f02e525 Mon Sep 17 00:00:00 2001
From: Christian Franke
Date: Sat, 14 Aug 2021 15:14:27 +0200
Subject: [PATCH] cygdrop: Fix printf format strings.
---
src/cygdrop/cygdrop.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/cygdrop/cygdrop.cc b/src/cygdrop/cygdrop.cc
index dc403c9..0c036bb 100644
--- a/src/cygdrop/cygdrop.cc
+++ b/src/cygdrop/cygdrop.cc
@@ -378,7 +378,7 @@ main (int argc, char **argv)
? " [logon_id]" : ""));
const struct group * g = strsid_to_group (strsid);
if (g)
- printf (" gid=%lu(%s)", g->gr_gid, g->gr_name);
+ printf (" gid=%u(%s)", (unsigned) g->gr_gid, g->gr_name);
printf ("\n");
}
@@ -415,7 +415,7 @@ main (int argc, char **argv)
printf ("r %s", strsid);
const struct group * g = strsid_to_group (strsid);
if (g)
- printf (" gid=%lu(%s)", g->gr_gid, g->gr_name);
+ printf (" gid=%u(%s)", (unsigned) g->gr_gid, g->gr_name);
printf ("\n");
}
--
2.32.0
--
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
[PATCH] cygutils-extra 1.4.16-3: cygdrop: Fix crash
Cygdrop from recent cygutils-extra crashes (only) after printing help text:
$ cygdrop
Usage: cygdrop [OPTIONS] COMMAND [ARG ...]
Group options
-l Disable local administrator group [default]
...
-v Verbose output, lists groups and privileges changed.
Repeat to list all groups and privileges.
*** stack smashing detected ***: terminated
Aborted (core dumped)
The root of the problem is a usually harmless bug introduced in 2010. A
function return type was declared as 'int' instead of 'void':
https://sourceware.org/git/?p=cygwin-apps/cygutils.git;a=commitdiff;h=517cf61
Newer g++ may then optimize away the function epilogue after inline
expansion. Here is a minimal testcase:
$ g++ --version
g++ (GCC) 10.2.0
...
$ cat test.cc
void f();
static int g()
{
f();
}
void h()
{
g();
}
$ g++ -S -O test.cc
test.cc: In function ‘int g()’:
test.cc:6:1: warning: no return statement in function returning non-void
[-Wreturn-type]
6 | }
| ^
$ c++filt < test.s
.file "test.cc"
.text
.globl h()
.def h(); .scl 2; .type 32; .endef
.seh_proc h()
h():
.LFB1:
subq $40, %rsp
.seh_stackalloc 40
.seh_endprologue
call f()
nop
.seh_endproc
.ident "GCC: (GNU) 10.2.0"
.def f(); .scl 2; .type 32; .endef
Problem and -Wreturn-type do not occur if compiled as a C program:
$ g++ -xc -S -O test.cc
$ cat test.s
...
h:
subq $40, %rsp
.seh_stackalloc 40
.seh_endprologue
call f
nop
addq $40, %rsp
ret
.seh_endproc
...
The problem also occurs with 32-bit Cygwin g++ and with current
MinGW-w64-g++ 32/64-bit.
Unfortunately GCC upstream has already set a related bug report to INVALID:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96181
I disagree...
Cygport should possibly add '-Werror=return-type' to C++ defaults.
Patch for cygutils is attached.
Regards,
Christian
From 330e4c8033ea17c312867906092397425d977c07 Mon Sep 17 00:00:00 2001
From: Christian Franke
Date: Sat, 14 Aug 2021 14:32:25 +0200
Subject: [PATCH] cygdrop: Fix return type of 'void' function.
This fixes a crash with recent versions of g++ (GCC Bugzilla 96181).
---
src/cygdrop/cygdrop.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/cygdrop/cygdrop.cc b/src/cygdrop/cygdrop.cc
index 35bcc19..dc403c9 100644
--- a/src/cygdrop/cygdrop.cc
+++ b/src/cygdrop/cygdrop.cc
@@ -39,7 +39,7 @@ static void help (FILE * f, const char *name);
static void version (FILE * f, const char *name);
static void license (FILE * f, const char *name);
-static int
+static void
usageCore (FILE * f, const char * name)
{
fprintf (f,
--
2.32.0
--
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] New: qemu-integration 1.1.0-1
The following packages have been uploaded to the Cygwin distribution: * qemu-integration-1.1.0-1 This package provides a transparent link based CLI integration for Qemu binaries and man pages. Default Qemu installation paths (e.g. for Qemu from https://qemu.weilnetz.de) are auto-detected, but are also configurable. The CLI integration links are auto-updated on each Cygwin Setup run. See /usr/share/doc/qemu-integration or https://gitlab.com/hejko-cygwin/qemu-integration/-/tree/1.1.0 for details. -- *** 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
New: qemu-integration 1.1.0-1
The following packages have been uploaded to the Cygwin distribution: * qemu-integration-1.1.0-1 This package provides a transparent link based CLI integration for Qemu binaries and man pages. Default Qemu installation paths (e.g. for Qemu from https://qemu.weilnetz.de) are auto-detected, but are also configurable. The CLI integration links are auto-updated on each Cygwin Setup run. See /usr/share/doc/qemu-integration or https://gitlab.com/hejko-cygwin/qemu-integration/-/tree/1.1.0 for details. -- *** 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: [ITP] Qemu
Am 14.08.21 um 13:26 schrieb Jon Turney: On 13/08/2021 09:52, Helge Konetzka wrote: Am 09.08.21 um 22:01 schrieb Jon Turney: On 09/08/2021 09:37, Helge Konetzka wrote: Am 04.08.21 um 15:03 schrieb Jon Turney: On 26/07/2021 21:15, Helge Konetzka wrote: Name: Helge Konetzka BEGIN SSH2 PUBLIC KEY Done. I've added 'qemu-integration' to your authorized uploads. Please see [1] for how to upload packages and push to the packaging git repository. [1] https://cygwin.com/packages.html Thanks, and sorry for the delay in processing this. I've uploaded the packages and pushed the cygport stuff. Is there anybody who wants to have a look before I add the ready-file? Looks good to me. Please go ahead. qemu-integration is available via Cygwin Setup since tuesday. I've manually sent the "cygport announce"-based text to cygwin-annou...@cygwin.com as proposed in https://cygwin.com/packaging-contributors-guide.html on wednesday. I am still waiting for delivery to the list... Is anything wrong with the mail? Is is lost perhaps? Just asking because I've seen a new ANNOUNCEMENT a few minutes ago Not sure what happened there. Please re-send the announcement. Done
Re: CI Build Job Shows Pending but Github Actions Scallywag shows Success Completed
On 13/08/2021 15:43, Brian Inglis wrote: CI build job 3160 gzip shown as still Pending https://cygwin.com/cgi-bin2/jobs.cgi?id=3160 but Github Actions Scallywag #146 job status shows Success and each arch shows as Completed https://github.com/cygwin/scallywag/actions/runs/1125132438 Yeah, there's something not 100% reliable in the way this event is processed (it seems like the metadata artifact url occasionally 404s if we try to fetch it immediately after the job completes) I've tried to add some resilience, but it seems it's still not there. I caused this event to get reprocessed, so it's status should be up to date now. I'll continue working on it, but please let me know if this happens again.
Re: [ITP] Qemu
On 13/08/2021 09:52, Helge Konetzka wrote: Am 09.08.21 um 22:01 schrieb Jon Turney: On 09/08/2021 09:37, Helge Konetzka wrote: Am 04.08.21 um 15:03 schrieb Jon Turney: On 26/07/2021 21:15, Helge Konetzka wrote: Name: Helge Konetzka BEGIN SSH2 PUBLIC KEY Done. I've added 'qemu-integration' to your authorized uploads. Please see [1] for how to upload packages and push to the packaging git repository. [1] https://cygwin.com/packages.html Thanks, and sorry for the delay in processing this. I've uploaded the packages and pushed the cygport stuff. Is there anybody who wants to have a look before I add the ready-file? Looks good to me. Please go ahead. qemu-integration is available via Cygwin Setup since tuesday. I've manually sent the "cygport announce"-based text to cygwin-annou...@cygwin.com as proposed in https://cygwin.com/packaging-contributors-guide.html on wednesday. I am still waiting for delivery to the list... Is anything wrong with the mail? Is is lost perhaps? Just asking because I've seen a new ANNOUNCEMENT a few minutes ago Not sure what happened there. Please re-send the announcement.
Re: Just updated cygutils and cygstart no longer works
Mark Geisert writes: > What I've figured out is that it's not the cygstart code itself that's > been mis-compiled, it's apparently code pulled in from libcygwin.a as > cygstart.exe is being built (on my machine before packaging). …in other words, the compiler used to create that has probably switched to some other psABI version as their default recently. > I do have different gcc/g++ options for building local cygwin1.dll and > libcygwin.a: "-O2 -march=native -mtune=native" Yeah. Never build libraries with these flags unless you are really sure you only ever use them on the same machine. Again, I recommend to have separate Cygwin installations for building packages that are kept as close to stock config as possible. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: Just updated cygutils and cygstart no longer works
Hi Achim, Achim Gratz wrote: Achim Gratz writes: The Cygwin gcc is configured to use -mtune=generic, …and -march=x86_64 on 64bit and -march=i686 on 32bit. While I'd love to switch to x86_64-v2, that would cut off a few processors that Win7 can be installed on. Thanks for the tips. Will do. What I've figured out is that it's not the cygstart code itself that's been mis-compiled, it's apparently code pulled in from libcygwin.a as cygstart.exe is being built (on my machine before packaging). I do have different gcc/g++ options for building local cygwin1.dll and libcygwin.a: "-O2 -march=native -mtune=native". The offending AVX instructions are located in _cygwin_crt0_common(). I also see a couple hundred other cases of AVX instructions within locally-built cygwin1.dll but those aren't important for resolving this issue. Sorry to any users who have or will run into this before it's fixed. If you're on a machine that supports AVX instructions you'll be OK. Otherwise, downgrading your cygutils packages to 1.4.16-2 will avoid the problem. ..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: Just updated cygutils and cygstart no longer works
Achim Gratz writes: > The Cygwin gcc is configured to use -mtune=generic, …and -march=x86_64 on 64bit and -march=i686 on 32bit. While I'd love to switch to x86_64-v2, that would cut off a few processors that Win7 can be installed on. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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: Just updated cygutils and cygstart no longer works
Mark Geisert writes: > I compiled the package with gcc 10.2.0 using the default options. Let > me investigate further to find some kind of solution for the AVX > usage, likely by using more/different gcc options. The Cygwin gcc is configured to use -mtune=generic, so if you're ending up with AVX instructions there must be something in the invocation that overrides either the tuning flags or the architecture flags. Getting rid of these things would be much preferrable over trying to undo whatever was done earlier as obviously if you get the order of these options wrong it might not work again. Check the environment and path settings and remove everything non-standard before starting the build (i.e just /usr/bin in the extreme). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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
