GNU implementation of the traditional m4 Unix macro processor.
Mostly SVR4 compatible with some extensions (for example, handling more than
9 positional macro parameters), also has built-in functions for including
files, running shell commands, doing arithmetic, and so on.

For more information see the project home pages:

        https://savannah.gnu.org/projects/m4/
        https://www.gnu.org/software/m4/

The following packages have been upgraded in the Cygwin distribution:

- m4    1.4.21

For changes since the previous Cygwin release, see below or read
/usr/share/doc/m4/NEWS after installation; for complete details see:

        https://lists.gnu.org/archive/html/m4-announce/2026-02/msg00000.html
        /usr/share/doc/m4/ChangeLog
        https://cgit.git.savannah.gnu.org/cgit/m4.git/log/?h=v1.4.21


2026-02-06      1.4.21

- Fix the `eval' builtin to reject input like `0x' that C does not
  accept as an integer literal, rather than silently treating it as zero
  (present since "the beginning").

- Fix the `define' and `pushdef' builtins to always warn when attempting
  to concatenate the result of using the `defn' macro on a builtin macro
  with anything else.
  This is a counterpart to the change in m4 1.4.11 that issues a warning
  when `defn' with multiple arguments attempts to perform concatenation.
  Attempting to use the output of `defn' anywhere other than a lone
  argument during macro definition has never been portable, but now the
  outcome is always the remaining text, rather than being dependent on
  whether `defn' was used before or after the other text
  (present since "the beginning").

- Port to glibc 2.43, which implements functions like strchr as macros
  when compiled with a C23 compiler.

-- 
              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
<https://cygwin.com/mailman/options/cygwin-announce>, and click 'Unsubscribe'.

If you need more information on unsubscribing, start reading here: 
<https://sourceware.org/lists.html#unsubscribe>.

Reply via email to