openembedded-core.git/meta/recipes-devtools/automake, branch thud

automake: fix race in parallel builds

2018-07-30T11:44:28+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

Signed-off-by: Hongxu Jia 
Signed-off-by: Richard Purdie

automake: 1.15.1 -> 1.16.1

2018-07-04T11:27:27+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

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

automake: refresh patches

2018-03-09T17:16: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.

Signed-off-by: Ross Burton 
Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

automake: Add missing libtool tag for cppasm language

2017-08-09T08:24:02+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.

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton

automake: 1.15 -> 1.15.1

2017-07-17T12:48:59+00:00

* Remove backported patch:
  - 0001-automake-port-to-Perl-5.22-and-later.patch

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

automake: Backport perl 5.22 fix

2017-05-23T16:43:58+00:00

Backport 13f00eb4493c "automake: port to Perl 5.22 and later"
from automake upstream to fix build with perl 5.22 .

Signed-off-by: Marek Vasut 
Cc: Ross Burton 
Cc: Richard Purdie 
Signed-off-by: Ross Burton

automake: Adjust shebang lines to remove interpreter path hardcode

2017-04-01T07:22:04+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 
Signed-off-by: Serhii Popovych 
Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T08:30:03+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\)

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

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

2016-06-02T10:45:26+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.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Richard Purdie

automake: don't delete .pyc files

2016-03-02T22:39:07+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.

Signed-off-by: Joseph A. Lutz 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie