From: Robert Yang <liezhi.yang@windriver.com>
To: Henning Heinold <henning@itconsulting-heinold.de>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] libtool: don't execute automake and autoconf on every invocation
Date: Thu, 12 Feb 2015 17:26:42 +0800 [thread overview]
Message-ID: <54DC71D2.3020607@windriver.com> (raw)
In-Reply-To: <20150212091423.GA18807@mail.itconsulting-heinold.de>
On 02/12/2015 05:14 PM, Henning Heinold wrote:
> On Thu, Feb 12, 2015 at 01:07:35AM -0800, Robert Yang wrote:
>> 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.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> meta/recipes-devtools/libtool/libtool-2.4.5.inc | 1 +
>> ...-t-execute-automake-and-autoconf-on-every.patch | 71 ++++++++++++++++++++
>> 2 files changed, 72 insertions(+)
>> create mode 100644 meta/recipes-devtools/libtool/libtool/libtool-don-t-execute-automake-and-autoconf-on-every.patch
>>
>> diff --git a/meta/recipes-devtools/libtool/libtool-2.4.5.inc b/meta/recipes-devtools/libtool/libtool-2.4.5.inc
>> index 88e281f..0f6bdc8 100644
>> --- a/meta/recipes-devtools/libtool/libtool-2.4.5.inc
>> +++ b/meta/recipes-devtools/libtool/libtool-2.4.5.inc
>> @@ -19,6 +19,7 @@ SRC_URI = "${GNU_MIRROR}/libtool/libtool-${PV}.tar.gz \
>> file://fix-resolve-lt-sysroot.patch \
>> file://nohardcodepaths.patch \
>> file://unwind-opt-parsing.patch \
>> + file://libtool-don-t-execute-automake-and-autoconf-on-every.patch \
>> "
>>
>> SRC_URI[md5sum] = "7d30ed9fa6bb11270ebb31639a37bd54"
>> diff --git a/meta/recipes-devtools/libtool/libtool/libtool-don-t-execute-automake-and-autoconf-on-every.patch b/meta/recipes-devtools/libtool/libtool/libtool-don-t-execute-automake-and-autoconf-on-every.patch
>> new file mode 100644
>> index 0000000..f48f09c
>> --- /dev/null
>> +++ b/meta/recipes-devtools/libtool/libtool/libtool-don-t-execute-automake-and-autoconf-on-every.patch
>> @@ -0,0 +1,71 @@
>> +From 408cfb9c5fa8a666917167ffb806cb19deded429 Mon Sep 17 00:00:00 2001
>> +From: "Gary V. Vaughan" <gary@gnu.org>
>> +Date: Fri, 6 Feb 2015 12:58:34 +0000
>> +Subject: [PATCH] libtool: don't execute automake and autoconf on every
>> + invocation.
>> +
>> +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.
>> +* NO-THANKS: Add Robert Yang.
>> +Reported by Robert Yang
>> +
>> +Signed-off-by: Gary V. Vaughan <gary@gnu.org>
>> +
>
> typo
>> +Updated: Change NO-THANKS to THANKS to apply the patch since upsream
> ^^^^^^^
Thanks, fixed in the repo.
// Robert
>> +renamed it.
>> +
>> +Upstream-Stauts: Backport
>> +
>> +Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> +
>> +---
>> + THANKS | 1 +
>> + build-aux/ltmain.in | 9 ++++++++-
>> + 2 files changed, 9 insertions(+), 1 deletion(-)
>> +
>> +diff --git a/THANKS b/THANKS
>> +index 0ab162d..aa7aa8c 100644
>> +--- a/THANKS
>> ++++ b/THANKS
>> +@@ -258,6 +258,7 @@ Robert Garron Robert.Garron@Access3000.net
>> + Robert Millan rmh@aybabtu.com
>> + Robert Ögren lists@roboros.com
>> + Roberto Bagnara bagnara@cs.unipr.it
>> ++Robert Yang liezhi.yang@windriver.com
>> + Roger Cornelius rac@tenzing.org
>> + Roland Mainz roland.mainz@nrubsig.org
>> + Roumen Petrov bugtrack@roumenpetrov.info
>> +diff --git a/build-aux/ltmain.in b/build-aux/ltmain.in
>> +index 46a0bb5..d5cf07a 100644
>> +--- a/build-aux/ltmain.in
>> ++++ b/build-aux/ltmain.in
>> +@@ -127,7 +127,12 @@ usage_message="Options:
>> + "
>> +
>> + # Additional text appended to 'usage_message' in response to '--help'.
>> +-long_help_message=$long_help_message"
>> ++func_help ()
>> ++{
>> ++ $debug_cmd
>> ++
>> ++ func_usage_message
>> ++ $ECHO "$long_help_message
>> +
>> + MODE must be one of the following:
>> +
>> +@@ -158,6 +163,8 @@ include the following information:
>> + Report bugs to <@PACKAGE_BUGREPORT@>.
>> + GNU @PACKAGE@ home page: <@PACKAGE_URL@>.
>> + General help using GNU software: <http://www.gnu.org/gethelp/>."
>> ++ exit 0
>> ++}
>> +
>> +
>> + # func_lo2o OBJECT-NAME
>
> Bye Henning
>
next prev parent reply other threads:[~2015-02-12 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 9:07 [PATCH 0/7] meta: several fixes Robert Yang
2015-02-12 9:07 ` [PATCH 1/7] Revert "libtool: avoid running automake/autoconf --version" Robert Yang
2015-02-12 9:07 ` [PATCH 2/7] libtool: don't execute automake and autoconf on every invocation Robert Yang
2015-02-12 9:14 ` Henning Heinold
2015-02-12 9:26 ` Robert Yang [this message]
2015-02-12 9:07 ` [PATCH 3/7] rt-tests: fix gzip command Robert Yang
2015-02-12 9:07 ` [PATCH 4/7] gcc-sanitizers: check gcc-build-internal before link Robert Yang
2015-02-12 9:07 ` [PATCH 5/7] btrfs-tools: fix for parallel build Robert Yang
2015-02-13 14:59 ` Burton, Ross
2015-02-12 9:07 ` [PATCH 6/7] btrfs-tools: remove nodocs.patch Robert Yang
2015-02-12 9:07 ` [PATCH 7/7] neard: do not ship version.h Robert Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DC71D2.3020607@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=henning@itconsulting-heinold.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.