[pkgsrc/trunk]: pkgsrc/devel/m4 Update to 1.4.9:

[wiz <wiz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/a1e87578e227
branches:  trunk
changeset: 527466:a1e87578e227
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Sun Apr 08 18:04:22 2007 +0000

description:
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.

diffstat:

 devel/m4/Makefile |  4 ++--
 devel/m4/distinfo |  8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diffs (25 lines):

diff -r 696f01ac0e43 -r a1e87578e227 devel/m4/Makefile
--- a/devel/m4/Makefile Sun Apr 08 18:00:08 2007 +0000
+++ b/devel/m4/Makefile Sun Apr 08 18:04:22 2007 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.45 2006/12/04 12:46:57 wiz Exp $
+# $NetBSD: Makefile,v 1.46 2007/04/08 18:04:22 wiz Exp $
 
-DISTNAME=      m4-1.4.8
+DISTNAME=      m4-1.4.9
 CATEGORIES=    devel
 MASTER_SITES=  ${MASTER_SITE_GNU:=m4/}
 
diff -r 696f01ac0e43 -r a1e87578e227 devel/m4/distinfo
--- a/devel/m4/distinfo Sun Apr 08 18:00:08 2007 +0000
+++ b/devel/m4/distinfo Sun Apr 08 18:04:22 2007 +0000
@@ -1,5 +1,5 @@
-$NetBSD: distinfo,v 1.14 2006/12/04 12:46:57 wiz Exp $
+$NetBSD: distinfo,v 1.15 2007/04/08 18:04:22 wiz Exp $
 
-SHA1 (m4-1.4.8.tar.gz) = 32b5bb526de9315d1a319c2ca8eb881d9b835506
-RMD160 (m4-1.4.8.tar.gz) = 933cc2acc7b65d1f3cff3b530852037b1e3d9bbe
-Size (m4-1.4.8.tar.gz) = 724448 bytes
+SHA1 (m4-1.4.9.tar.gz) = 15ad35c65d4c4f2f856687288e7f6b51704d65e1
+RMD160 (m4-1.4.9.tar.gz) = 5833efd8aaec3f60cff9997ca7cf15cc7a7ea3c1
+Size (m4-1.4.9.tar.gz) = 770647 bytes