linux/poky.git/meta/recipes-devtools/libtool/libtool-2.4.5.inc, branch hardknott-next

libtool: 2.4.5 -> 2.4.6

2015-02-17T13:43:38+00:00

Drop patch merged upstream. (From OE-Core rev: cd03ef79b50ed42b9d407ee45fc3e3321385281c) Signed-off-by: Richard Purdie

libtool: don't execute automake and autoconf on every invocation

2015-02-15T21:58:25+00:00

From the origin commit message: Regression from 2.4.2 was causing noticable slow-down in builds that call libtool many times. * build-aux/ltmain.in (func_help): Override func_help() from gl/build-aux/options-parser to only run automake --version and autoconf --version when libtool --help is executed on the command line. (From OE-Core rev: 9fd23c9ac03143b578559bb79995f2655c81ccc8) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

Revert "libtool: avoid running automake/autoconf --version"

2015-02-15T21:58:25+00:00

This reverts commit 1f53edeaf9ea59dd55459a6d5a93829fb4983839. There is a better fix on upstream, will backport it. (From OE-Core rev: 600c9bb271a47674876b029a6a58ffac08add8ed) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

libtool: Fix option parsing performance regression

2015-02-10T22:36:38+00:00

Cut and paste the pieces of build-aux/options-parser inline into the main ltmain.sh code. This removes a performance degradation caused by the repeated calls to func_quote_for_eval, the mechanism funclib uses to construct the functions used for option parsing. (From OE-Core rev: 6bf5cbbcac80ee818cc932d69227e70e41ce02d3) Signed-off-by: Richard Purdie

libtool: avoid running automake/autoconf --version

2015-02-05T09:46:11+00:00

The libtool would be very slow if run "automake/autoconf --version", for example, when compile xz-native (make -j1, only compile, no confiure or install): before patched: 19s after patched: 11s Use plain text to instead of running them. NOTE: it is still a little slower than libtool 2.4.2 when compile xz-native because of other parts: make -j1: about 2s slower make -j32: about 0.4s slower If we run to do_install: (PARALLEL_MAKE = "-j32") libtool 2.4.2: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.092s user 0m28.292s sys 0m3.932s libtool 2.4.5: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.380s user 0m31.140s sys 0m4.068s About 0.3s, slightly different. But when using /bin/bash as CONFIG_SHELL, the new libtool would be much slower: real 0m23.106s user 0m44.044s sys 0m4.280s About 2s slower, for the big package like cairo, it is more slower (about 6s), unfortunately, /bin/bash is most default CONFIG_SHELL for the recipes since configure checks first check bash. (From OE-Core rev: eb9d896db2fc67bac8efd258744d06fbbee87f06) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

libtool: Fix tools path issues

2015-02-03T14:30:55+00:00

If for example you build on a machine with /bin/grep, then restore that sstate onto a machine with /usr/bin/grep, things will fail. Simply don't bother hardcoding paths. This was lost during the libtool upgrade: http://git.yoctoproject.org/cgit.cgi/poky/diff/meta/recipes-devtools/libtool/libtool/avoid_absolute_paths_for_general_utils.patch?id=d4e1862453b2a4c12400de0f43f08a9871a4de60 since the path to the files changed. This restores the previous behaviour. (From OE-Core rev: e48c06264f183c3d611a20a45914e9eeaa8f3736) Signed-off-by: Richard Purdie

libtool: 2.4.4 -> 2.4.5

2015-02-02T14:09:20+00:00

(From OE-Core rev: 8156469a2ff36521aefcc9a3a4125d2dbcd4711a) Signed-off-by: Richard Purdie