2008-04-27 02:01:56 by Jeremy C. Reed | Files touched by this commit (1) |
Log message:
Fix homepage.
|
2008-04-13 02:51:59 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Add patch from Bruno Haible (upstream) fixing two of the included
gnulib tests that were broken on NetBSD-4.99.58/amd64.
Bump PKGREVISION.
|
2008-04-13 00:43:15 by Johnny C. Lam | Files touched by this commit (370) |
Log message:
Convert to use PLIST_VARS instead of manually passing "@comment "
through PLIST_SUBST to the plist module.
|
2007-09-25 03:23:24 by Dan McMahill | Files touched by this commit (2) |
Log message:
add hacks.mk to work around a compiler optimization error with
gcc on solaris.
|
2007-07-29 16:36:47 by Joerg Sonnenberger | Files touched by this commit (5) |
Log message:
Override gnulib's fflush.c on DragonFly with a far less intrusive
versions. This is still in discussion with upstream, but working m4
is critical, so apply this stop-gap solution. It works on the other
BSD derived stdio implementations as well, if you want to switch.
|
2007-07-22 08:34:41 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
Update to 1.4.10nb1. Like previous update to 1.4.10, but includes
a patch from Eric Blake that fixes the problem that appeared e.g.
in dosbox or mng.
|
2007-07-20 00:13:44 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Update to 1.4.10. Add commented out LICENSE=GPLv3 line.
Version 1.4.10 - 09 Jul 2007, by Eric Blake (CVS version 1.4.9c)
* Upgrade from GPL version 2 to GPL version 3 or later.
* A number of portability improvements inherited from gnulib.
* Avoid undefined behavior introduced in 1.4.9b in the `format' builtin
when handling %c. However, this area of code has never been documented,
and currently does not match the POSIX behavior of printf(1), so it may
have further changes in the next version.
Version 1.4.9b - 29 May 2007, by Eric Blake (CVS version 1.4.9a)
* Fix regression introduced in 1.4.9 in the `eval' builtin when performing
division.
* Fix regression introduced in 1.4.8 in the `-F' option that made it
impossible to freeze more than 512 kibibytes of diverted text.
* The synclines option `-s' no longer generates sync lines in the middle of
multiline comments or quoted strings.
* Work around a number of corner-case POSIX compliance bugs in various
broken stdio libraries. In particular, the `syscmd' builtin behaves
more predictably when stdin is seekable.
* The `format' builtin now understands formats such as %a, %A, and %'hhd,
and works around a number of platform printf bugs. Furthermore, the
sequence format(%*.*d,-1,-1,1) no longer outputs random data. However,
some non-compliant platforms such as mingw still have known bugs in
strtod that may cause testsuite failures.
* The testsuite is improved to also run gnulib portability tests for the
features that M4 imports from gnulib.
|
2007-05-24 23:51:47 by Dan McMahill | Files touched by this commit (3) |
Log message:
Fix a division bug when negative numbers are involved. Bump pkgrev.
|
2007-04-08 20:04:23 by Thomas Klausner | Files touched by this commit (2) |
Log message:
Update to 1.4.9:
Version 1.4.9 - 23 Mar 2007, by Eric Blake (CVS version 1.4.8c)
* Minor documentation and portability cleanups.
Version 1.4.8b - 24 Feb 2007, by Eric Blake (CVS version 1.4.8a)
* Fix a regression introduced in 1.4.8 that made m4 unable to process
files larger than 2GiB on some platforms.
* Fix a regression introduced in 1.4.8 that made m4 dump core when
invoked as 'm4 -- file'.
* The `eval' builtin now follows C precedence rules. Additionally, the
short-circuit operators correctly short-circuit division by zero. The
previously undocumented alias of '=' meaning '==' in eval now triggers a
deprecation warning, so that a future version of M4 can implement a form
of variable assignment as an extension.
* The `include' builtin now affects exit status on failure, as required by
POSIX. Use `sinclude' if you need a successful exit status.
* The `-E'/`--fatal-warnings' command-line option now has two levels. When
specified only once, warnings affect exit status, but execution
continues, so that you can see all warnings instead of fixing them one
at a time. To acheive 1.4.8 behavior, where the first warning
immediately exits, specify -E twice on the command line.
* A new `--warn-macro-sequence' command-line option allows detection of
sequences in `define' and `pushdef' definitions that match an optional
regular expression. The default regular expression is
`\$\({[^}]*}\|[0-9][0-9]+\)', corresponding to the sequences that might
not behave correctly when upgrading to the eventual M4 2.0. By default,
M4 2.0 will follow the POSIX requirement that a macro definition
containing `$11' must expand to the first argument concatenated with 1,
rather than the eleventh argument; and will take advantage of the POSIX
wording that allows implementations to treat `${11}' as the eleventh
argument instead of literal text. Be aware that Autoconf 2.61 will not
work with this option enabled with the default regular expression; but
Autoconf 2.62 will be compatible with this option.
* Improved portability to platforms such as BSD/OS and AIX.
|
2006-12-04 13:46:57 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Update to 1.4.8:
Version 1.4.8 - 20 November 2006, by Eric Blake (CVS version 1.4.7a)
* The `divert' macro and `-H'/`--hashsize' command line option no longer
cause a core dump when handed extra large values. Also, `divert' now
uses memory proportional to the number of diversions in use, rather than
to the maximum diversion number encountered, so that large diversion
numbers are less likely to exhaust system memory; and is no longer
limited by the maximum number of file descriptors.
* The `--help' and `--version' command line options now consistently
override all earlier options. For example, `m4 --debugfile=trace
--help' now no longer accidentally creates an empty file `trace'.
* The `-L'/`--nesting-limit' command line option can now be set to 0
to remove the default limit of 1024. However, it is still possible that
heavily nested input can cause abrupt program termination due to stack
overflow.
* Problems encountered when writing to standard error, such as with the
`errprint' macro, now always cause a non-zero exit status.
* Warnings and errors issued during macro expansion are now consistently
reported at the line where the macro name was detected, rather than
where the close parenthesis resides. Text wrapped by `m4wrap' now
remembers the location that was in effect when m4wrap was invoked,
rather than changing to line 0 and the empty string for a file. The
macros `__line__' and `__file__' now work correctly even as the last
token in an included file.
* The `builtin' and `indir' macros now transparently handle builtin
tokens generated by `defn'.
* When diversions created by the `divert' macro collect enough text that
M4 must use temporary files, the environment variable $TMPDIR is now
consulted, and a better effort is made to clean up those files in the
event of a fatal signal.
* The `mkstemp' builtin is added with the same GNU semantics as `maketemp',
based on the recommendation of POSIX to deprecate the POSIX semantics of
`maketemp' as inherently insecure. In GNU mode (no -G supplied on the
command line), `maketemp' silently retains the secure GNU semantics, but
a future release of M4 will change this to emit a warning. In
traditional mode (m4 -G), `maketemp' now uses the POSIX-mandated insecure
semantics, and issues a warning that you should convert your script to
use `mkstemp' instead. Additionally, `mkstemp' and `maketemp' are now
well-defined even if the template argument does not end in six `X'
characters.
* The manual has been improved, including a new section on a composite
macro `foreach'.
* The `changecom' and `changequote' macros now treat an empty second
argument the same as if it were missing, rather than using the empty
string and making it impossible to end a comment or quote.
* The `translit' macro now operates in linear instead of quadratic time,
and is now eight-bit clean.
* The `-D', `-U', `-s', and `-t' command line options now take effect
after any files encountered earlier on the command line, rather than up
front, as is done in traditional implementations and required by POSIX.
|