summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/libtool/libtool/avoid-running-automake-autoconf-version.patch
AgeCommit message (Collapse)Author
2015-02-15Revert "libtool: avoid running automake/autoconf --version"Robert Yang
This reverts commit 1f53edeaf9ea59dd55459a6d5a93829fb4983839. There is a better fix on upstream, will backport it. (From OE-Core rev: 600c9bb271a47674876b029a6a58ffac08add8ed) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-05libtool: avoid running automake/autoconf --versionRobert Yang
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 <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>