diff options
author | Robert Yang <liezhi.yang@windriver.com> | 2015-02-05 01:31:28 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-02-05 09:46:11 +0000 |
commit | 1f53edeaf9ea59dd55459a6d5a93829fb4983839 (patch) | |
tree | ca39c21f342a3aee55fb798619ae126ee0fd7eb2 /scripts | |
parent | d8f0011c23a6b8441323974acc70b08c81cfefbd (diff) | |
download | poky-1f53edeaf9ea59dd55459a6d5a93829fb4983839.tar.gz |
libtool: avoid running automake/autoconf --version
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>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions