Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] gettext: optimize build time
Date: Thu, 29 May 2014 13:20:36 +0200	[thread overview]
Message-ID: <20140529132036.3b24cc80@free-electrons.com> (raw)
In-Reply-To: <20140529105623.GN20069@tarshish>

Dear Baruch Siach,

On Thu, 29 May 2014 13:56:23 +0300, Baruch Siach wrote:

> > Thanks to these changes, the build time of gettext goes from 1 minutes
> > and 37 seconds to just 24 seconds, and the build of host-gettext goes
> > from 2 minutes and 18 seconds to 1 minute and 13 seconds.
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> >  .../gettext-03-option-to-disable-tools.patch       | 42 ----------------------
> 
> Why not remove --disable-tools from GETTEXT_CONF_OPT then?

Indeed, thanks for noticing. I'll fix that up in v2.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-05-29 11:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 10:40 [Buildroot] [PATCH 0/3] Speed-up gettext and host-gettext build Thomas Petazzoni
2014-05-29 10:40 ` [Buildroot] [PATCH 1/3] minidlna: do not select BR2_PACKAGE_GETTEXT_TOOLS Thomas Petazzoni
2014-05-29 10:40 ` [Buildroot] [PATCH 2/3] gettext: remove support for gettext-tools on target Thomas Petazzoni
2014-05-29 13:04   ` Thomas De Schampheleire
2014-05-29 10:40 ` [Buildroot] [PATCH 3/3] gettext: optimize build time Thomas Petazzoni
2014-05-29 10:56   ` Baruch Siach
2014-05-29 11:20     ` Thomas Petazzoni [this message]
2014-05-30 18:31 ` [Buildroot] [PATCH 0/3] Speed-up gettext and host-gettext build Andrew Ruder

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=20140529132036.3b24cc80@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox