linux/poky.git/meta/recipes-devtools/automake, branch pyro

automake: Backport perl 5.22 fix

2017-06-14T10:56:49+00:00

Backport 13f00eb4493c "automake: port to Perl 5.22 and later" from automake upstream to fix build with perl 5.22 . (From OE-Core rev: ab0e298ec2c155739565f1cde76639855ba7bba0) Signed-off-by: Marek Vasut Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: Adjust shebang lines to remove interpreter path hardcode

2017-04-01T22:28:20+00:00

If build host perl (and other tools) is old and we use some kind of toolchain to provide recent perl/python/etc to the OE build we still locked to use build host perl due to hardcoded shebang lines in automake scripts. Behaviour was observed with Enterprise Linux 6 and devtoolset toolchain from SCL (Software Collections) used to provide recent version of perl (not provided with default buildtools-tarball). Pass /usr/bin/env perl in ac_cv_path_PERL configuration variables for class-native and class-nativesdk. Use patch to automake to replace -w option in shebang line with modern way to enable warnings on perl (i.e. "use warnings"). Also add nativesdk-autoconf to RDEPENDS to bring runtime dependencies inline with other targets. Note that ac_cv_path_PERL must be valid perl interpreter path since configure will check perl version and Flock implementation. It is not possible currently to use nativeperl from native sysroot because automake does not DEPENDS on perl-native (and doing so fails due to circular dependencies). Only possible solution is to overwrite shebangs with nativeperl somewhere at do_install() and update RDEPENDS for class-native. Or add perl symlinks to nativeperl in sysroot. For now it seems good to use perl found by /usr/bin/env from automake-native. Cc: XE-Linux (From OE-Core rev: 3b7111b30dbd9a4cdd141b594164da18c15ae970) Signed-off-by: Serhii Popovych Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: drop the Python scriptlets to determine Python's directories

2016-06-03T12:13:28+00:00

python.m4 has python scriptlets that determine where the system's library directory is. For Python 2.x distutils.sysconfig is used (which works because we patch it), for Python 3.x plain sysconfig is used (which doesn't work for example on x32). There is also a hardcoded fallback if the scriptlets fail. This commit removes the scriptlets altogether and just uses the hardcoded path always, due to above mentioned issues with x32. (From OE-Core rev: 0c856653ce65403791e1e5c78229820ff794bae3) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

automake: don't delete .pyc files

2016-03-02T22:39:45+00:00

The patch being removed in this commit removes *.pyc files from being compiled. This dose not allow a user to select which files are included in the image. Since optimization is no longer the default for python we should have the ability to choose what is included in the image. (From OE-Core rev: bee0f633f0b5ef2439b8e5d54cbfc7bc1f17f47e) Signed-off-by: Joseph A. Lutz Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: set test-driver path relative to top_builddir

2016-02-28T11:33:03+00:00

automake offers auxiliary tools and is capable to install and prepare the setup for those. test-driver, a log driver used by parallel testsuite harness in ptests, is one of those tools. By default it looks that automake prepare environment for testing relative $top_srcdir. But in Yocto following changed: - build folder was separated - $top_srcdir is not anymore defined as relative path, now can be relative or absolute So now in Yocto the Makefile from src/tests contains absolute path of $top_srcdir for test-driver which is an unexisting path at runtime. We need to have relative path for test-driver in Makefile to work on target. $top_builddir can guarantee this path. Originally submitted by Adrian Calianu (From OE-Core rev: e9db0ae11d95f3c375b27d5c10606efd8b568fbf) Signed-off-by: Martin Borg Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: rename perl-native-runtime

2016-01-11T23:26:31+00:00

The code in native.bbclass adds -native suffix to the package names that don't have it. perl-native-runtime becomes perl-native-runtime-native because of this. Renamed perl-native-runtime -> hostperl-runtime-native to avoid mangling it and to conform with the naming convetion for native packages. (From OE-Core rev: f4dade8e765a8c7bfd131728b9e0a34631e24950) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: Remove delays in configure scripts using automake

2015-12-14T22:30:56+00:00

By default automake puts "sleep 1" into the start of configure scripts which adds pointless delays to them. Rather than do this, lets just assume our systems are sane. Since this means our patches touch m4 files, we need to stop automake running autoreconf so we tweak the do_configure to avoid this. (From OE-Core rev: 25eca6793cd4ad7af7e23669ed4f47d075ec696d) Signed-off-by: Richard Purdie

automake: simplify perl location forcing logic

2015-05-15T21:08:03+00:00

Instead of letting configure find the host's perl and then use a complicated sed to replace it at install time, simply pre-seed the configure logic with the path we want to use. (From OE-Core rev: 84a3978653a322583d413d795567fa431ac7c952) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: upgrade to 1.15

2015-01-23T11:36:26+00:00

(From OE-Core rev: 455edf38e8af854de0cffffdebf258b354ff7e54) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie