add a missing word in perllexwarn
assume "all" in "use warnings 'FATAL';" and related

Until now, the behavior of the statements

 use warnings "FATAL";
 use warnings "NONFATAL";
 no warnings "FATAL";

was unspecified and inconsistent. This change causes them to be handled
with an implied "all" at the end of the import list.

Tony Cook: fix AUTHORS formatting
[perl #120977] bump $warnings::VERSION
[perl #120977] use warnings "FATAL" implies "all"
perldelta for c91312d5e, none needed for e214621be
Regenerate from meta after backporting crosscompile changes

I am sure there are items that could have been processed even cleaner,
but with the current state, the content is functional equal.
restore missed commit in regeneration (spotted by hugmeir)
Configure: Split the usecrosscompile section from the to/from/run section

Beyond organization, this also makes sure that usecrosscompile is
always set to undef if we're not cross-compiling, which enables
code to realibly use $Config{usecrosscompile} to check for a
cross-compiling perl.
Configure: Set to/from/run scripts if targethost is passed

Do this regardless of whether we are cross compiling
add an escape for when targethost is not defined but usecrosscompile is.

See http://www.nntp.perl.org/group/perl.perl5.porters/2012/12/msg196443.html
"Cross-building and Makefile.SH", which explains the reasoning for this.
fix the ability to use targethost when defined.
Update AUTHORS and MANIFEST to appease test_porting
Stop using $run for anything other than testing compiled tests in Configure.

When cross-compiling we want to run miniperl etc on the compile host, not the test target
Stop using Config{run} to check the version of (mini)perl we are running
Build host miniperl and generate_uudmap binaries when cross compiling, for local use
Run all the miniperl calls locally, not via RUN
configpm should use "osname" from config.sh, instead of miniperl's $^O.

This is necessary when cross-compiliing, as we use a host (mini)perl to
run configpm for the target arch; so for example, miniperl's $^O
might be 'linux', but config.sh's osname can be 'qnx'.
write_buildcustomize.pl: Setup $^O to be the target os when building Core.

This allows the correct hints files to be loaded when building modules
We do this by giving write_buildcustomize.pl a 'osname' parameter.

This means that write_buildcustomize.pl no longer depends on
Config to get osname, which eliminates a circular dependency
in the Makefiles.
Makefile.SH: Updated the lib/buildcustomize.pl rule for cross-compilation builds
Use the system perl for RUN_PERL, if we are cross compiling, and we found one.

Note we can only substitute the system perl for scripts that do not require Config
as it complains about non-matching Perl versions.