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

automake: fix race in parallel builds

2018-07-30T11:44:34+00:00

While native building, there is a parallel failure [snip] |: && mkdir -p doc && ./pre-inst-env /usr/bin/env perl ../automake-1.16.1/doc/help2man --output=doc/aclocal-1.16.1 aclocal-1.16 |help2man: can't get `--help' info from aclocal-1.16 |Try `--no-discard-stderr' if option outputs to stderr Makefile:3693: recipe for target 'doc/aclocal-1.16.1' failed [snip] Correct Makefile rule to fix the issue (From OE-Core rev: ef4907f311e3ddedfa3eb8a111cc1d146c19851a) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

automake: 1.15.1 -> 1.16.1

2018-07-04T23:22:08+00:00

* Refreshed the following patches: - 0001-automake-Add-default-libtool_tag-to-cppasm.patch - automake-replace-w-option-in-shebangs-with-modern-use-warnings.patch - buildtest.patch - new_rt_path_for_test-driver.patch - performance.patch - python-libdir.patch (From OE-Core rev: f63a493298de7d0cac36a65dafba5dae06c06a05) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

automake: refresh patches

2018-03-09T17:17:03+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: d29d95e627b2303b835a705cb7d55d1e41ddb0a7) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: Add missing libtool tag for cppasm language

2017-08-09T08:24:16+00:00

This is highlighted when CC is passing flags like -fPIE which are stripped by libtool when building shared libs and replaced with -fPIC, this actually results in CC not matching the CC computed from cmdline created for compiling and as a result libtool heuristic to compute tags auotmatically fails. (From OE-Core rev: 519c34adeb0735f6ff606addd00a7bbe19f4b15c) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: 1.15 -> 1.15.1

2017-07-17T13:01:38+00:00

* Remove backported patch: - 0001-automake-port-to-Perl-5.22-and-later.patch (From OE-Core rev: 6455aa2289a401ab4959b399acada02907be99be) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

automake: Backport perl 5.22 fix

2017-05-23T16:45:36+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: 7fa044e799db651d45e4732e2527acfc2bc7cd47) Signed-off-by: Marek Vasut Cc: Ross Burton Cc: Richard Purdie 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