[pkgsrc/trunk]: pkgsrc/devel/bison bison: update to 3.4.2

To: pkgsrc-changes-hg%NetBSD.org@localhost
Subject: [pkgsrc/trunk]: pkgsrc/devel/bison bison: update to 3.4.2
From: triaxx <triaxx%pkgsrc.org@localhost>
Date: Wed, 23 Oct 2019 13:11:41 +0000
details:   https://anonhg.NetBSD.org/pkgsrc/rev/358bfd5a0759
branches:  trunk
changeset: 342655:358bfd5a0759
user:      triaxx <triaxx%pkgsrc.org@localhost>
date:      Wed Oct 23 12:17:33 2019 +0000

description:
bison: update to 3.4.2

upstream changes:
-----------------
GNU Bison NEWS

* Noteworthy changes in release 3.4.2 (2019-09-12) [stable]

** Bug fixes

  In some cases, when warnings are disabled, bison could emit tons of white
  spaces as diagnostics.

  When running out of memory, bison could crash (found by fuzzing).

  When defining twice the EOF token, bison would crash.

  New warnings from recent compilers have been addressed in the generated
  parsers (yacc.c, glr.c, glr.cc).

  When lone carriage-return characters appeared in the input file,
  diagnostics could hang forever.

* Noteworthy changes in release 3.4.1 (2019-05-22) [stable]

** Bug fixes

  Portability fixes.

* Noteworthy changes in release 3.4 (2019-05-19) [stable]

** Deprecated features

  The %pure-parser directive is deprecated in favor of '%define api.pure'
  since Bison 2.3b (2008-05-27), but no warning was issued; there is one
  now.  Note that since Bison 2.7 you are strongly encouraged to use
  '%define api.pure full' instead of '%define api.pure'.

** New features

*** Colored diagnostics

  As an experimental feature, diagnostics are now colored, controlled by the
  new options --color and --style.

  To use them, install the libtextstyle library before configuring Bison.
  It is available from

    https://alpha.gnu.org/gnu/gettext/

  for instance

    https://alpha.gnu.org/gnu/gettext/libtextstyle-0.8.tar.gz

  The option --color supports the following arguments:
    - always, yes: Enable colors.
    - never, no: Disable colors.
    - auto, tty (default): Enable colors if the output device is a tty.

  To customize the styles, create a CSS file similar to

    /* bison-bw.css */
    .warning   { }
    .error     { font-weight: 800; text-decoration: underline; }
    .note      { }

  then invoke bison with --style=bison-bw.css, or set the BISON_STYLE
  environment variable to "bison-bw.css".

*** Disabling output

  When given -fsyntax-only, the diagnostics are reported, but no output is
  generated.

  The name of this option is somewhat misleading as bison does more than
  just checking the syntax: every stage is run (including checking for
  conflicts for instance), except the generation of the output files.

*** Include the generated header (yacc.c)

  Before, when --defines is used, bison generated a header, and pasted an
  exact copy of it into the generated parser implementation file.  If the
  header name is not "y.tab.h", it is now #included instead of being
  duplicated.

  To use an '#include' even if the header name is "y.tab.h" (which is what
  happens with --yacc, or when using the Autotools' ylwrap), define
  api.header.include to the exact argument to pass to #include.  For
  instance:

    %define api.header.include {"parse.h"}

  or

    %define api.header.include {<parser/parse.h>}

*** api.location.type is now supported in C (yacc.c, glr.c)

  The %define variable api.location.type defines the name of the type to use
  for locations.  When defined, Bison no longer defines YYLTYPE.

  This can be used in programs with several parsers to factor their
  definition of locations: let one of them generate them, and the others
  just use them.

** Changes

*** Graphviz output

  In conformance with the recommendations of the Graphviz team, if %require
  "3.4" (or better) is specified, the option --graph generates a *.gv file
  by default, instead of *.dot.

*** Diagnostics overhaul

  Column numbers were wrong with multibyte characters, which would also
  result in skewed diagnostics with carets.  Beside, because we were
  indenting the quoted source with a single space, lines with tab characters
  were incorrectly underlined.

  To address these issues, and to be clearer, Bison now issues diagnostics
  as GCC9 does.  For instance it used to display (there's a tab before the
  opening brace):

    foo.y:3.37-38: error: $2 of ?expr? has no declared type
     expr: expr '+' "number"        { $$ = $1 + $2; }
                                         ^~
  It now reports

    foo.y:3.37-38: error: $2 of ?expr? has no declared type
        3 | expr: expr '+' "number" { $$ = $1 + $2; }
          |                                     ^~

  Other constructs now also have better locations, resulting in more precise
  diagnostics.

*** Fix-it hints for %empty

  Running Bison with -Wempty-rules and --update will remove incorrect %empty
  annotations, and add the missing ones.

*** Generated reports

  The format of the reports (parse.output) was improved for readability.

*** Better support for --no-line.

  When --no-line is used, the generated files are now cleaner: no lines are
  generated instead of empty lines.  Together with using api.header.include,
  that should help people saving the generated files into version control
  systems get smaller diffs.

** Documentation

  A new example in C shows an simple infix calculator with a hand-written
  scanner (examples/c/calc).

  A new example in C shows a reentrant parser (capable of recursive calls)
  built with Flex and Bison (examples/c/reccalc).

  There is a new section about the history of Yaccs and Bison.

** Bug fixes

  A few obscure bugs were fixed, including the second oldest (known) bug in
  Bison: it was there when Bison was entered in the RCS version control
  system, in December 1987.  See the NEWS of Bison 3.3 for the previous
  oldest bug.

* Noteworthy changes in release 3.3.2 (2019-02-03) [stable]

** Bug fixes

  Bison 3.3 failed to generate parsers for grammars with unused nonterminal
  symbols.

* Noteworthy changes in release 3.3.1 (2019-01-27) [stable]

** Changes

  The option -y/--yacc used to imply -Werror=yacc, which turns uses of Bison
  extensions into errors.  It now makes them simple warnings (-Wyacc).

* Noteworthy changes in release 3.3 (2019-01-26) [stable]

  A new mailing list was created, Bison Announce.  It is low traffic, and is
  only about announcing new releases and important messages (e.g., polls
  about major decisions to make).

  https://lists.gnu.org/mailman/listinfo/bison-announce

** Backward incompatible changes

  Support for DJGPP, which has been unmaintained and untested for years, is
  removed.

** Deprecated features

  A new feature, --update (see below) helps adjusting existing grammars to
  deprecations.

*** Deprecated directives

  The %error-verbose directive is deprecated in favor of '%define
  parse.error verbose' since Bison 3.0, but no warning was issued.

  The '%name-prefix "xx"' directive is deprecated in favor of '%define
  api.prefix {xx}' since Bison 3.0, but no warning was issued.  These
  directives are slightly different, you might need to adjust your code.
  %name-prefix renames only symbols with external linkage, while api.prefix
  also renames types and macros, including YYDEBUG, YYTOKENTYPE,
  yytokentype, YYSTYPE, YYLTYPE, etc.

  Users of Flex that move from '%name-prefix "xx"' to '%define api.prefix
  {xx}' will typically have to update YY_DECL from

    #define YY_DECL int xxlex (YYSTYPE *yylval, YYLTYPE *yylloc)

  to

    #define YY_DECL int xxlex (XXSTYPE *yylval, XXLTYPE *yylloc)

*** Deprecated %define variable names

  The following variables, mostly related to parsers in Java, have been
  renamed for consistency.  Backward compatibility is ensured, but upgrading
  is recommended.

    abstract           -> api.parser.abstract
    annotations        -> api.parser.annotations
    extends            -> api.parser.extends
    final              -> api.parser.final
    implements         -> api.parser.implements
    parser_class_name  -> api.parser.class
    public             -> api.parser.public
    strictfp           -> api.parser.strictfp

** New features

*** Generation of fix-its for IDEs/Editors

  When given the new option -ffixit (aka -fdiagnostics-parseable-fixits),
  bison now generates machine readable editing instructions to fix some
  issues.  Currently, this is mostly limited to updating deprecated
  directives and removing duplicates.  For instance:

    $ cat foo.y
    %error-verbose
    %define parser_class_name "Parser"
    %define api.parser.class "Parser"
    %%
    exp:;

  See the "fix-it:" lines below:

    $ bison -ffixit foo.y
    foo.y:1.1-14: warning: deprecated directive, use '%define parse.error verbose' [-Wdeprecated]
     %error-verbose
     ^~~~~~~~~~~~~~
    fix-it:"foo.y":{1:1-1:15}:"%define parse.error verbose"
    foo.y:2.1-34: warning: deprecated directive, use '%define api.parser.class {Parser}' [-Wdeprecated]
     %define parser_class_name "Parser"
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    fix-it:"foo.y":{2:1-2:35}:"%define api.parser.class {Parser}"
    foo.y:3.1-33: error: %define variable 'api.parser.class' redefined
     %define api.parser.class "Parser"
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    foo.y:2.1-34:     previous definition
     %define parser_class_name "Parser"
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    fix-it:"foo.y":{3:1-3:34}:""
    foo.y: warning: fix-its can be applied.  Rerun with option '--update'. [-Wother]

  This uses the same output format as GCC and Clang.

*** Updating grammar files

  Fixes can be applied on the fly.  The previous example ends with the
  suggestion to re-run bison with the option -u/--update, which results in a
  cleaner grammar file.

    $ bison --update foo.y
    [...]
    bison: file 'foo.y' was updated (backup: 'foo.y~')

    $ cat foo.y
    %define parse.error verbose
    %define api.parser.class {Parser}
    %%
    exp:;

*** Bison is now relocatable

  If you pass '--enable-relocatable' to 'configure', Bison is relocatable.

  A relocatable program can be moved or copied to a different location on
  the file system.  It can also be used through mount points for network
  sharing.  It is possible to make symbolic links to the installed and moved
  programs, and invoke them through the symbolic link.

*** %expect and %expect-rr modifiers on individual rules

  One can now document (and check) which rules participate in shift/reduce
  and reduce/reduce conflicts.  This is particularly important GLR parsers,
  where conflicts are a normal occurrence.  For example,

      %glr-parser
      %expect 1
      %%

      ...

      argument_list:
        arguments %expect 1
      | arguments ','
      | %empty
      ;

      arguments:
        expression
      | argument_list ',' expression
      ;

      ...

  Looking at the output from -v, one can see that the shift-reduce conflict
  here is due to the fact that the parser does not know whether to reduce
  arguments to argument_list until it sees the token _after_ the following
  ','.  By marking the rule with %expect 1 (because there is a conflict in
  one state), we document the source of the 1 overall shift-reduce conflict.

  In GLR parsers, we can use %expect-rr in a rule for reduce/reduce
  conflicts.  In this case, we mark each of the conflicting rules.  For
  example,

      %glr-parser
      %expect-rr 1

      %%

      stmt:
        target_list '=' expr ';'
      | expr_list ';'
      ;

      target_list:
        target
      | target ',' target_list
      ;

      target:
        ID %expect-rr 1
      ;

      expr_list:
        expr
      | expr ',' expr_list
      ;

      expr:
        ID %expect-rr 1
      | ...
      ;

  In a statement such as

      x, y = 3, 4;

  the parser must reduce x to a target or an expr, but does not know which
  until it sees the '='.  So we notate the two possible reductions to
  indicate that each conflicts in one rule.

  This feature needs user feedback, and might evolve in the future.

*** C++: Actual token constructors

  When variants and token constructors are enabled, in addition to the
  type-safe named token constructors (make_ID, make_INT, etc.), we now
  generate genuine constructors for symbol_type.

  For instance with these declarations

    %token           ':'
       <std::string> ID
       <int>         INT;

  you may use these constructors:

    symbol_type (int token, const std::string&);
    symbol_type (int token, const int&);
    symbol_type (int token);

  Correct matching between token types and value types is checked via
  'assert'; for instance, 'symbol_type (ID, 42)' would abort.  Named
  constructors are preferable, as they offer better type safety (for
  instance 'make_ID (42)' would not even compile), but symbol_type
  constructors may help when token types are discovered at run-time, e.g.,

     [a-z]+   {
                if (auto i = lookup_keyword (yytext))
                  return yy::parser::symbol_type (i);
                else
                  return yy::parser::make_ID (yytext);
              }

*** C++: Variadic emplace

  If your application requires C++11 and you don't use symbol constructors,
  you may now use a variadic emplace for semantic values:

    %define api.value.type variant
    %token <std::pair<int, int>> PAIR

  in your scanner:

    int yylex (parser::semantic_type *lvalp)
    {
      lvalp->emplace <std::pair<int, int>> (1, 2);
      return parser::token::PAIR;
    }

*** C++: Syntax error exceptions in GLR

  The glr.cc skeleton now supports syntax_error exceptions thrown from user
  actions, or from the scanner.

*** More POSIX Yacc compatibility warnings

  More Bison specific directives are now reported with -y or -Wyacc.  This
  change was ready since the release of Bison 3.0 in September 2015.  It was
  delayed because Autoconf used to define YACC as `bison -y`, which resulted
  in numerous warnings for Bison users that use the GNU Build System.

  If you still experience that problem, either redefine YACC as `bison -o
  y.tab.c`, or pass -Wno-yacc to Bison.

*** The tables yyrhs and yyphrs are back

  Because no Bison skeleton uses them, these tables were removed (no longer
  passed to the skeletons, not even computed) in 2008.  However, some users
  have expressed interest in being able to use them in their own skeletons.

** Bug fixes

*** Incorrect number of reduce-reduce conflicts

  On a grammar such as

     exp: "num" | "num" | "num"

  bison used to report a single RR conflict, instead of two.  This is now
  fixed.  This was the oldest (known) bug in Bison: it was there when Bison
  was entered in the RCS version control system, in December 1987.

  Some grammar files might have to adjust their %expect-rr.

*** Parser directives that were not careful enough

  Passing invalid arguments to %nterm, for instance character literals, used
  to result in unclear error messages.

** Documentation

  The examples/ directory (installed in .../share/doc/bison/examples) has
  been restructured per language for clarity.  The examples come with a
  README and a Makefile.  Not only can they be used to toy with Bison, they
  can also be starting points for your own grammars.

  There is now a Java example, and a simple example in C based on Flex and
  Bison (examples/c/lexcalc/).

** Changes

*** Parsers in C++

  They now use noexcept and constexpr.  Please, report missing annotations.

*** Symbol Declarations

  The syntax of the variation directives to declare symbols was overhauled
  for more consistency, and also better POSIX Yacc compliance (which, for
  instance, allows "%type" without actually providing a type).  The %nterm
  directive, supported by Bison since its inception, is now documented and
  officially supported.

  The syntax is now as follows:

    %token TAG? ( ID NUMBER? STRING? )+ ( TAG ( ID NUMBER? STRING? )+ )*
    %left  TAG? ( ID NUMBER? )+ ( TAG ( ID NUMBER? )+ )*
    %type  TAG? ( ID | CHAR | STRING )+ ( TAG ( ID | CHAR | STRING )+ )*
    %nterm TAG? ID+ ( TAG ID+ )*

  where TAG denotes a type tag such as ?<ival>?, ID denotes an identifier
  such as ?NUM?, NUMBER a decimal or hexadecimal integer such as ?300? or
  ?0x12d?, CHAR a character literal such as ?'+'?, and STRING a string
  literal such as ?"number"?.  The post-fix quantifiers are ??? (zero or
  one), ?*? (zero or more) and ?+? (one or more).

diffstat:

 devel/bison/Makefile |    5 +-
 devel/bison/PLIST    |  125 ++++++++++++++++++++++++++++++++++++++------------
 devel/bison/distinfo |   10 ++--
 3 files changed, 102 insertions(+), 38 deletions(-)

diffs (246 lines):

diff -r defb7ba9bd7e -r 358bfd5a0759 devel/bison/Makefile
--- a/devel/bison/Makefile      Wed Oct 23 11:59:03 2019 +0000
+++ b/devel/bison/Makefile      Wed Oct 23 12:17:33 2019 +0000
@@ -1,7 +1,6 @@
-# $NetBSD: Makefile,v 1.108 2019/10/23 11:58:01 triaxx Exp $
+# $NetBSD: Makefile,v 1.109 2019/10/23 12:17:33 triaxx Exp $
 
-DISTNAME=      bison-3.2.4
-PKGREVISION=   2
+DISTNAME=      bison-3.4.2
 CATEGORIES=    devel
 MASTER_SITES=  ${MASTER_SITE_GNU:=bison/}
 EXTRACT_SUFX=  .tar.xz
diff -r defb7ba9bd7e -r 358bfd5a0759 devel/bison/PLIST
--- a/devel/bison/PLIST Wed Oct 23 11:59:03 2019 +0000
+++ b/devel/bison/PLIST Wed Oct 23 12:17:33 2019 +0000
@@ -1,118 +1,183 @@
-@comment $NetBSD: PLIST,v 1.31 2019/10/23 11:58:01 triaxx Exp $
+@comment $NetBSD: PLIST,v 1.32 2019/10/23 12:17:33 triaxx Exp $
 bin/bison
 info/bison.info
 man/man1/bison.1
 share/aclocal/bison-i18n.m4
-share/bison/README
-share/bison/bison.m4
-share/bison/c++-skel.m4
-share/bison/c++.m4
-share/bison/c-like.m4
-share/bison/c-skel.m4
-share/bison/c.m4
-share/bison/glr.c
-share/bison/glr.cc
-share/bison/java-skel.m4
-share/bison/java.m4
-share/bison/lalr1.cc
-share/bison/lalr1.java
-share/bison/location.cc
+share/bison/README.md
+share/bison/bison-default.css
 share/bison/m4sugar/foreach.m4
 share/bison/m4sugar/m4sugar.m4
-share/bison/stack.hh
-share/bison/variant.hh
+share/bison/skeletons/README-D.txt
+share/bison/skeletons/bison.m4
+share/bison/skeletons/c++-skel.m4
+share/bison/skeletons/c++.m4
+share/bison/skeletons/c-like.m4
+share/bison/skeletons/c-skel.m4
+share/bison/skeletons/c.m4
+share/bison/skeletons/d-skel.m4
+share/bison/skeletons/d.m4
+share/bison/skeletons/glr.c
+share/bison/skeletons/glr.cc
+share/bison/skeletons/java-skel.m4
+share/bison/skeletons/java.m4
+share/bison/skeletons/lalr1.cc
+share/bison/skeletons/lalr1.d
+share/bison/skeletons/lalr1.java
+share/bison/skeletons/location.cc
+share/bison/skeletons/stack.hh
+share/bison/skeletons/variant.hh
+share/bison/skeletons/yacc.c
 share/bison/xslt/bison.xsl
 share/bison/xslt/xml2dot.xsl
 share/bison/xslt/xml2text.xsl
 share/bison/xslt/xml2xhtml.xsl
-share/bison/yacc.c
 share/doc/bison/AUTHORS
 share/doc/bison/COPYING
 share/doc/bison/NEWS
 share/doc/bison/README
 share/doc/bison/THANKS
 share/doc/bison/TODO
-share/doc/bison/examples/README
+share/doc/bison/examples/README.md
 share/doc/bison/examples/c++/Makefile
-share/doc/bison/examples/c++/README
+share/doc/bison/examples/c++/README.md
+share/doc/bison/examples/c++/calc++/Makefile
+share/doc/bison/examples/c++/calc++/README.md
+share/doc/bison/examples/c++/calc++/calc++.cc
+share/doc/bison/examples/c++/calc++/driver.cc
+share/doc/bison/examples/c++/calc++/driver.hh
+share/doc/bison/examples/c++/calc++/parser.yy
+share/doc/bison/examples/c++/calc++/scanner.ll
 share/doc/bison/examples/c++/simple.yy
 share/doc/bison/examples/c++/variant-11.yy
 share/doc/bison/examples/c++/variant.yy
-share/doc/bison/examples/calc++/Makefile
-share/doc/bison/examples/calc++/README
-share/doc/bison/examples/calc++/calc++.cc
-share/doc/bison/examples/calc++/driver.cc
-share/doc/bison/examples/calc++/driver.hh
-share/doc/bison/examples/calc++/parser.yy
-share/doc/bison/examples/calc++/scanner.ll
-share/doc/bison/examples/mfcalc/calc.h
-share/doc/bison/examples/mfcalc/mfcalc.y
-share/doc/bison/examples/rpcalc/rpcalc.y
+share/doc/bison/examples/c/README.md
+share/doc/bison/examples/c/calc/Makefile
+share/doc/bison/examples/c/calc/README.md
+share/doc/bison/examples/c/calc/calc.y
+share/doc/bison/examples/c/lexcalc/Makefile
+share/doc/bison/examples/c/lexcalc/README.md
+share/doc/bison/examples/c/lexcalc/parse.y
+share/doc/bison/examples/c/lexcalc/scan.l
+share/doc/bison/examples/c/mfcalc/Makefile
+share/doc/bison/examples/c/mfcalc/calc.h
+share/doc/bison/examples/c/mfcalc/mfcalc.y
+share/doc/bison/examples/c/reccalc/Makefile
+share/doc/bison/examples/c/reccalc/README.md
+share/doc/bison/examples/c/reccalc/parse.y
+share/doc/bison/examples/c/reccalc/scan.l
+share/doc/bison/examples/c/rpcalc/Makefile
+share/doc/bison/examples/c/rpcalc/rpcalc.y
+share/doc/bison/examples/d/Makefile
+share/doc/bison/examples/d/README.md
+share/doc/bison/examples/d/calc.y
+share/doc/bison/examples/java/Calc.y
+share/doc/bison/examples/java/Makefile
+share/doc/bison/examples/java/README.md
+${PLIST.nls}share/locale/af/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ast/LC_MESSAGES/bison-runtime.mo
+${PLIST.nls}share/locale/be/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/bg/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/bg/LC_MESSAGES/bison-runtime.mo
+${PLIST.nls}share/locale/bg/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ca/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ca/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ca/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/cs/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/da/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/da/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/da/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/de/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/de/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/de/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/el/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/el/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/el/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/eo/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/eo/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/eo/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/es/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/es/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/es/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/et/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/et/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/et/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/eu/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/fi/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/fi/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/fi/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/fr/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/fr/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/fr/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ga/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ga/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ga/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/gl/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/gl/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/hr/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/hr/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/hu/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/hu/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ia/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/id/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/id/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/it/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/it/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/it/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ja/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ja/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ja/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ko/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ky/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/lt/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/lv/LC_MESSAGES/bison-runtime.mo
+${PLIST.nls}share/locale/ms/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ms/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ms/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/nb/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/nb/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/nb/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/nl/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/nl/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/nl/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/pl/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/pl/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/pl/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/pt/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/pt/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/pt/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ro/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ro/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ro/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/ru/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/ru/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/ru/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/rw/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/sk/LC_MESSAGES/bison-gnulib.mo
+${PLIST.nls}share/locale/sl/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/sl/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/sq/LC_MESSAGES/bison-runtime.mo
+${PLIST.nls}share/locale/sr/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/sr/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/sr/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/sv/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/sv/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/sv/LC_MESSAGES/bison.mo
 ${PLIST.nls}share/locale/th/LC_MESSAGES/bison-runtime.mo
+${PLIST.nls}share/locale/tr/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/tr/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/tr/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/uk/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/uk/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/uk/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/vi/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/vi/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/vi/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/bison.mo
+${PLIST.nls}share/locale/zh_TW/LC_MESSAGES/bison-gnulib.mo
 ${PLIST.nls}share/locale/zh_TW/LC_MESSAGES/bison-runtime.mo
 ${PLIST.nls}share/locale/zh_TW/LC_MESSAGES/bison.mo
diff -r defb7ba9bd7e -r 358bfd5a0759 devel/bison/distinfo
--- a/devel/bison/distinfo      Wed Oct 23 11:59:03 2019 +0000
+++ b/devel/bison/distinfo      Wed Oct 23 12:17:33 2019 +0000
@@ -1,7 +1,7 @@
-$NetBSD: distinfo,v 1.50 2019/02/13 20:05:14 wiz Exp $
+$NetBSD: distinfo,v 1.51 2019/10/23 12:17:33 triaxx Exp $
 
-SHA1 (bison-3.2.4.tar.xz) = 950c7fa571677828eab963126b93a4ed9d496b74
-RMD160 (bison-3.2.4.tar.xz) = 901b1c5357009604983d002c55d48d09ab750884
-SHA512 (bison-3.2.4.tar.xz) = 652b54fdee969bbc17eeb04d05d65f143e8e0e1b46ac2574e3a76687b9bd916c9a0c97658b4f8357958d64e87fe2a6a2a98a6c312970f0e74fb4445962e9daae
-Size (bison-3.2.4.tar.xz) = 2094568 bytes
+SHA1 (bison-3.4.2.tar.xz) = 5aa25aad924da6eda6df03a697f59d85081c5551
+RMD160 (bison-3.4.2.tar.xz) = 00d7179f584b13b8b37c564c2d52d1d0b423b3c0
+SHA512 (bison-3.4.2.tar.xz) = 00d2b37187b93100ec4b220ce2752d12ccf68f9d0d39b380d375d36dd8a22aa1d6e60156918f95e4493f9531c5d42d8fad38fd807307b491c1ca7ca4177823d9
+Size (bison-3.4.2.tar.xz) = 2240532 bytes
 SHA1 (patch-lib_isnan.c) = 5b44fc6e2e97e36f91cd784bf3a38ad459fccdab
Prev by Date: [pkgsrc/trunk]: pkgsrc/doc doc: Updated devel/bison to 3.4.2
Next by Date: [pkgsrc/trunk]: pkgsrc/inputmethod/tc (inputmethod/tc) Fix build for new emac...
Previous by Thread: [pkgsrc/trunk]: pkgsrc/doc doc: Updated devel/bison to 3.4.2
Next by Thread: [pkgsrc/trunk]: pkgsrc/inputmethod/tc (inputmethod/tc) Fix build for new emac...
Indexes:
Home | Main Index | Thread Index | Old Index