take maintainership
On BSD use <sys/endian.h> to derive endianess, instead of defaulting
to little endian always.
+ autoconf-2.69, automake-1.12
Update to 2.69:

* Noteworthy changes in release 2.69 (2012-04-24) [stable]

** Autoconf now requires perl 5.6 or better (but generated configure
   scripts continue to run without perl).

* Noteworthy changes in release 2.68b (2012-03-01) [beta]
  Released by Eric Blake, based on git versions 2.68.*.

** Autoconf-generated configure scripts now unconditionally re-execute
   themselves with $CONFIG_SHELL, if that's set in the environment.

** The texinfo documentation no longer specifies "front-cover" or
   "back-cover" texts, so that it may now be included in Debian's
   "main" section.

** Support for the Go programming language has been added.  The new macro
   AC_LANG_GO sets variables GOC and GOFLAGS.

** AS_LITERAL_IF again treats '=' as a literal.  Regression introduced in
   2.66.

** The macro AS_EXECUTABLE_P, present since 2.50, is now documented.

** Macros

- AC_PROG_LN_S and AS_LN_S now fall back on 'cp -pR' (not 'cp -p') if 'ln -s'
  does not work.  This works better for symlinks to directories.

- New macro AC_HEADER_CHECK_STDBOOL.

- New and updated macros for Fortran support:

    AC_FC_CHECK_BOUNDS to enable array bounds checking
    AC_F77_IMPLICIT_NONE and AC_FC_IMPLICIT_NONE to disable implicit integer
    AC_FC_MODULE_EXTENSION to compute the Fortran 90 module name extension
    AC_FC_MODULE_FLAG for the Fortran 90 module search path flag
    AC_FC_MODULE_OUTPUT_FLAG for the Fortran 90 module output directory flag
    AC_FC_PP_SRCEXT for preprocessed Fortran source files extensions
    AC_FC_PP_DEFINE for the Fortran preprocessor define flag
Updated devel/autoconf to 2.69
Update to 1.12:

* WARNING: Future backward-incompatibilities!

  - Starting from the next major Automake version (1.13), the rules to
    build pdf, ps and dvi output from Texinfo input will use the '--tidy'
    option by default.  Since such an option was introduced in Texinfo
    4.9, this means that Makefiles generated by future Automake versions
    will require at least that version of Texinfo.

  - Starting from the next major Automake version (1.13), the parallel
    testsuite harness (previously only enabled by the 'parallel-tests'
    option) will become the default one; the older serial testsuite
    harness will still be available through the use of the 'serial-tests'
    option.

  - The following long-obsolete m4 macros will be removed in the
    next major Automake version (1.13):

      AM_PROG_CC_STDC:    superseded by AC_PROG_CC since October 2002
      fp_PROG_CC_STDC:    broken alias for AM_PROG_CC_STDC
      fp_WITH_DMALLOC:    old alias for AM_WITH_DMALLOC
      AM_CONFIG_HEADER:   superseded by AC_CONFIG_HEADERS since July 2002
      ud_PATH_LISPDIR:    old alias for AM_PATH_LISPDIR
      jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
      ud_GNU_GETTEXT:     old alias for AM_GNU_GETTEXT
      gm_PROG_LIBTOOL:    old alias for AC_PROG_LIBTOOL
      fp_C_PROTOTYPES:    old alias for AM_C_PROTOTYPES (which was part
                          of the now-removed automatic de-ANSI-fication
                          support of Automake)

  - All the "old alias" macros in 'm4/obsolete.m4' will be removed in
    the next major Automake version (1.13).

  - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option)
    will be deprecated in the next minor version of Automake (1.12.1) and
    removed in the next major version (1.13).

  - Support for the two- and three-arguments invocation forms of the
    AM_INIT_AUTOMAKE macro will be deprecated in the next minor version
    of Automake (1.12.1) and removed in the next major version (1.13).

  - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
    variable, @mkdir_p@ substitution and AM_PROG_MKDIR m4 macro will
    all be deprecated in the next minor version of Automake (1.12.1)
    and removed in the next major version (1.13).

  - The '--acdir' option of aclocal is deprecated, and will probably
    be removed in the next major Automake release (1.13).  You should
    use the options '--automake-acdir' and '--system-acdir' instead
    (which have been introduced in Automake 1.11.2).

  - The exact order in which the directories in the aclocal macro
    search path are looked up is probably going to be changed in the
    next Automake release (1.13).

* Obsolete features removed:

  - The never documented nor truly used script 'acinstall' has been
    removed.

  - Support for automatic de-ANSI-fication has been removed.

  - The support for the "obscure" multilib feature has been removed
    from Automake core (but remains available in the 'contrib/'
    directory of the Automake distribution).

  - Support for ".log -> .html" conversion and the check-html and
    recheck-html targets has been removed from Automake core (but
    remains available in the 'contrib/' directory of the Automake
    distribution).

  - The deprecated 'lzma' compression format for distribution archives
    has been removed, in favor of 'xz' and 'lzip'.

  - The obsolete AM_WITH_REGEX macro has been removed.

  - The long-deprecated options '--output-dir', '--Werror' and
    '--Wno-error' have been removed.

  - The chapter on the history of Automake has been moved out of the
    reference manual, into a new dedicated Texinfo file.

* New targets:

  - New 'cscope' target to build a cscope database for the source tree.

* Changes to Automake-generated testsuite harnesses:

  - The new automake option 'serial-tests' has been introduced.  It can
    be used to explicitly instruct automake to use the older serial
    testsuite harness.  This is still the default at the moment, but it
    might change in future versions.

  - The 'recheck' target (provided by the parallel testsuite harness) now
    depends on the 'all' target.  This allows for a better user-experience
    in test-driven development.  See automake bug#11252.

  - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
    and unexpected or internal error, or a failure to set up the test case
    scenario) have their outcome reported as an 'ERROR' now.  Previous
    versions of automake reported such an outcome as a 'FAIL' (the only
    difference with normal failures being that hard errors were counted
    as failures even when the test originating them was listed in
    XFAIL_TESTS).

  - The testsuite summary displayed by the parallel-test harness has a
    completely new format, that always list the numbers of passed, failed,
    xfailed, xpassed, skipped and errored tests, even when these numbers
    are zero (but using smart coloring when the color-tests option is in
    effect).

  - The default testsuite driver offered by the 'parallel-tests' option is
    now implemented (partly at least) with the help of automake-provided
    auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
    on code in the generated Makefile.in.
    This has two noteworthy implications.  The first one is that projects
    using the 'parallel-tests' option should now either run automake with
    the '--add-missing' option, or manually copy the 'test-driver' script
    into their tree.  The second, and more important, implication is that
    now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
    not be used anymore to define a test runner, and the command specified
    in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
    program or script.  For example, this is still a valid usage (albeit
    a little contorted):

      TESTS_ENVIRONMENT = \
        if test -n '$(STRICT_TESTS)'; then \
          maybe_errexit='-e'; \
        else \
          maybe_errexit=''; \
        fi;
      LOG_COMPILER = $(SHELL) $$maybe_errexit

    while this is not anymore:

      TESTS_ENVIRONMENT = \
        $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`

    neither is this:

      TESTS_ENVIRONMENT = \
        run_with_perl_or_shell () \
        { \
          if grep -q '^#!.*perl' $$1; then
            $(PERL) $$1; \
          else \
            $(SHELL) $$1; \
          fi; \
        }
      LOG_COMPILER = run_with_perl_or_shell

  - The package authors can now use customary testsuite drivers within
    the framework provided by the 'parallel-tests' testsuite harness.
    Consistently with the existing syntax, this can be done by defining
    special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.

  - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
    to redirect/define file descriptors used by the test scripts.

  - The parallel-tests harness generates now, in addition the '.log' files
    holding the output produced by the test scripts, a new set of '.trs'
    files, holding "metadata" derived by the execution of the test scripts;
    among such metadata are the outcomes of the test cases run by a script.

  - Initial and still experimental support for the TAP test protocol is
    now provided.

* Changes to Yacc and Lex support:

  - C source and header files derived from non-distributed Yacc and/or
    Lex sources are now removed by a simple "make clean" (while they were
    previously removed only by "make maintainer-clean").

  - Slightly backward-incompatible change, relevant only for use of Yacc
    with C++: the extensions of the header files produced by the Yacc
    rules are now modelled after the extension of the corresponding
    sources.  For example, yacc files named "foo.y++" and "bar.yy" will
    produce header files named "foo.h++" and "bar.hh" respectively, where
    they would have previously produced header files named simply "foo.h"
    and "bar.h".  This change offers better compatibility with 'bison -o'.

* Miscellaneous changes:

  - The AM_PROG_VALAC macro now causes configure to exit with status 77,
    rather than 1, if the vala compiler found is too old.

  - The build system of Automake itself now avoids the use of make
    recursion as much as possible.

  - Automake now prefers to quote 'like this' or "like this", rather
    than `like this', in diagnostic message and generated Makefiles,
    to accommodate the new GNU Coding Standards recommendations.

  - Automake has a new option '--print-libdir' that prints the path of the
    directory containing the Automake-provided scripts and data files.

  - The 'dist' and 'dist-all' targets now can run compressors in parallel.

  - The rules to create pdf, dvi and ps output from Texinfo files now
    works better with modern 'texi2dvi' script, by explicitly passing
    it the '--clean' option to ensure stray auxiliary files are not
    left to clutter the build directory.

  - Automake can now generate silenced rules for texinfo outputs.

  - Some auxiliary files that are automatically distributed by Automake
    (e.g., 'install-sh', or the 'depcomp' script for packages compiling
    C sources) might now be listed in the DIST_COMMON variable in many
    Makefile.in files, rather than in the top-level one.

  - Messages of types warning or error from 'automake' and 'aclocal'
    are now prefixed with the respective type, and presence of -Werror
    is noted.

  - Automake's early configure-time sanity check now tries to avoid
    sleeping for a second, which slowed down cached configure runs
    noticeably.  In that case, it will check back at the end of the
    configure script to ensure that at least one second has passed, to
    avoid time stamp issues with makefile rules rerunning autotools
    programs.

  - The warnings in the category 'extra-portability' are now enabled by
    '-Wall'.  In previous versions, one has to use '-Wextra-portability'
    to enable them.

Bugs fixed in 1.12:

  - Various minor bugfixes for recent or long-standing bugs.

* Bugs introduced by 1.11:

  - The AM_COND_IF macro also works if the shell expression for the
    conditional is no longer valid for the condition.

  - The automake-provided parallel testsuite harness does not fail anymore
    with BSD make used in parallel mode when there are test scripts in a
    subdirectory, like in:

      TESTS = sub/foo.test sub/bar.test

* Long-standing bugs:

  - Automake's own build system finally have a real "installcheck" target.

  - Vala-related cleanup rules are now more complete, and work better in
    a VPATH setup.

  - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
    now automatically distributed also if the directory of the auxiliary
    files coincides with the top-level directory.

  - Automake now detects the presence of the '-d' flag in the various
    '*YFLAGS' variables even when their definitions involve indirections
    through other variables, such as in:
      foo_opts = -d
      AM_YFLAGS = $(foo_opts)

  - Automake now complains if a '*YFLAGS' variable has any conditional
    content, not only a conditional definition.

  - Explicit enabling and/or disabling of Automake warning categories
    through the '-W...' options now always takes precedence over the
    implicit warning level implied by Automake strictness (foreign, gnu
    or gnits), regardless of the order in which such strictness and
    warning flags appear.  For example, a setting like:
      AUTOMAKE_OPTIONS = -Wall --foreign
    will cause the warnings in category 'portability' to be enabled, even
    if those warnings are by default disabled in 'foreign' strictness.
Updated devel/automake to 1.12
If EMUL_IS_NATIVE (i.e. on Linux) several X libraries, alsa-lib and unixodbc
are needed.

Bump PKGREVISION.
Updated lang/sun-jre6 to 6.0.31nb1
Initial import of picoc-2.1 into the Packages Collection

	PicoC is a very small C interpreter for scripting.  It was originally
	written as the script language for a UAV's on-board flight system.
	It's also very suitable for other robotic, embedded and non-embedded
	applications.

	The core C source code is around 4000 lines of code.  It's not
	intended to be a complete implementation of ISO C but it has all the
	essentials.  When compiled it only takes a few k of code space and is
	also very sparing of data space.  This means it can work well in small
	embedded devices.  It's also a fun example of how to create a very
	small language implementation while still keeping the code readable.

	picoc has been tested on x86-32, x86-64, powerpc, arm, ultrasparc,
	HP-PA and blackfin processors and is easy to port to new targets.

To show it working on the old DECUS grep program (included as one of its
tests):

	% time picoc work/picoc/tests/46_grep.c - case work/picoc/tests/46_grep.c
	File work/picoc/tests/46_grep.c:
	"lower-case are always ignored.  Blank lines never match.  The expression",

	      case '^':

	      case '$':

	      case '.':

	      case '[':

	      case ':':
	...
	0.651u 0.000s 0:00.68 95.5%     0+0k 0+0io 0pf+0w
	% wc work/picoc/tests/46_grep.c 
	      557    1991   15172 work/picoc/tests/46_grep.c
	%
Merge from vendor branch TNF:
Initial import of picoc-2.1 into the Packages Collection

	PicoC is a very small C interpreter for scripting.  It was originally
	written as the script language for a UAV's on-board flight system.
	It's also very suitable for other robotic, embedded and non-embedded
	applications.

	The core C source code is around 4000 lines of code.  It's not
	intended to be a complete implementation of ISO C but it has all the
	essentials.  When compiled it only takes a few k of code space and is
	also very sparing of data space.  This means it can work well in small
	embedded devices.  It's also a fun example of how to create a very
	small language implementation while still keeping the code readable.

	picoc has been tested on x86-32, x86-64, powerpc, arm, ultrasparc,
	HP-PA and blackfin processors and is easy to port to new targets.

To show it working on the old DECUS grep program (included as one of its
tests):

	% time picoc work/picoc/tests/46_grep.c - case work/picoc/tests/46_grep.c
	File work/picoc/tests/46_grep.c:
	"lower-case are always ignored.  Blank lines never match.  The expression",

	      case '^':

	      case '$':

	      case '.':

	      case '[':

	      case ':':
	...
	0.651u 0.000s 0:00.68 95.5%     0+0k 0+0io 0pf+0w
	% wc work/picoc/tests/46_grep.c 
	      557    1991   15172 work/picoc/tests/46_grep.c
	%
Add and enable picoc
Note addition of lang/picoc version 2.1
Improve the patch that adds the %M spec string to handle multilib_os_dir
being NULL.

When building a single ABI capable gcc (e.g. 32bit systems), multilib_os_dir
may be NULL and this would cause gcc to segfault when trying to link libgcc.

Thanks to Filip Hajny for isolating the problem to the %M patch.
Do not enable largefile support on SunOS.
PR 46383 by Uwe Klaus.
Update sysutils/ruby-rb-appscript to 0.6.1.


2010-03-19 -- 0.6.1

* removed 32-bit only AE.run_application_event_loop,
  AE.quit_application_event_loop
* updated AE.launch_application to use LSOpenApplication
* minor documentation fixes


2010-12-17 -- 0.6.0

* added UTF-8 Encoding support in Ruby 1.9+; added
  AEMCodecs::Codecs#use_ascii_8bit for optionally disabling it
* AEM::Codecs#pack now accepts Date, DateTime instances; added
  AEM::Codecs#use_date_time method for unpacking typeLongDateTime descriptors
  as DateTime instead of Time instances
* removed AE.get_app_terminology() as it relied on deprecated Carbon APIs
* added AE.copy_scripting_definition()
* the OSAX module now now uses OSACopyScriptingDefinition() to obtain
  scripting addition terminology, so works in both 32- and 64-bit Ruby. Note
  that in addition to limitations of OSACopyScriptingDefinition
  (e.g. aete-to-sdef conversion is not 100% reliable), the SdefParser is
  limited in capability (no support for xi:include, class-extension, synonym
  elements), but should suffice for parsing relatively simple osax
  dictionaries.
* modified Terminology.dump() to retrieve aete resources via 'ascrgdte'
  events; added OSAX.dump() method
* added workaround for transaction id bug in some versions of OS X 10.6
* renamed AEMReference::Base class to AEMReference::Query
* renamed Send::CommandError class to Send::EventError; note that AEM
  re-exports it as AEM::EventError and [for backwards compatibilty]
  AEM::CommandError


2009-07-18 -- 0.5.3

* fixed pALL code in defaultterminology
* fixed OSAX module initialisation code (previously didn't initialise if
  ScriptingAddition.new was called directly)
* fixed out-of-date URLs in appscript manual


2009-07-05 -- 0.5.2

* removed deprecated AEM::Application.is_running? method
* added #dont_cache_unpacked_specifiers, #pack_strings_as_type compatibility
  options to AEM::Codecs
* added default definitions for 'item' type, 'items' elements, 'properties'
  property as Apple have removed the 'item' class definition from
  skeleton.sdef (the default terminology for Cocoa apps)
* property and elements methods now raise ArgumentError if passed arguments;
  previously, malformed elements selectors,
  e.g. app('TextEdit').documents(1).text, would be silently ignored, resulting
  in unexpected behaviour
* Codecs#unpack now tries to coerce descriptors of typeVersion to unicode text
  (works on 10.4+) c.f. AppleScript (note: itunes.version.get returns the
  wrong version number otherwise; this appears to be an iTunes bug, but is
  masked by current AppleScript behaviour)
* #process_exists_for_url?, #remote_app in connect.rb now raise error if URL
   string doesn't contain a colon (process will crash otherwise due to an OS
   bug)
* improved error reporting in Reference#[] when a malformed generic reference
  containing a command expands to a non-reference value. e.g. its.name.get()
  would previously expand the the value of the object's 'name' property,
  typically a string, resulting in a cryptic NoMethodError; this now raises a
  descriptive ArgumentError.
* fixed bug where Terminology module would error on zero-length keywords in
  problem dictionaries (e.g. MS Word 12.1.7)
* AEM::Codecs now correctly unpacks AEDescs of typeBoolean whose data >1 byte
* fixed inconsistent escaping of application-defined property/element names
  that overlap built-in type/enum/property names but uses different
  codes. e.g. Adobe Illustrator defines 'rotation' as 'SxRx' - this overlaps
  built-in definition ('rotation' = 'trot'), so is escaped as
  'rotation_'. Previously only the Keyword was escaped (i.e. :rotation_ but
  ref.rotation) now both are escaped (i.e. :rotation_, ref.rotation_). Users
  should update existing code as needed.
* restructured defaultterminology.rb to make it easier to maintain
* changed default terminology mapping for :data from KAE::CRawData ('rdat') to
  KAE::TypeData ('tdta')
* the OSAX module now obtains list of installed scripting additions on first
  use instead of import (the .osax scanning code uses System Events via AEM,
  and sending Apple events in event loop-based application before the event
  loop is started can disrupt the process's handling of incoming Apple events)
Note update of sysutils/ruby-rb-appscript package to 0.6.1.
expect builtin gcc atomic functions for gcc>=4.1.
Recursive bump from icu shlib major bumped to 49.
Fix CVE-2009-2688, via <https://bugzilla.redhat.com/show_bug.cgi?id=511994>