All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] infra: add gettextize run in AUTORECONF
Date: Mon, 14 Jul 2014 13:01:04 +0200	[thread overview]
Message-ID: <20140714130104.480ab4cf@free-electrons.com> (raw)
In-Reply-To: <1405186024-8170-2-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Sat, 12 Jul 2014 14:27:03 -0300, Gustavo Zacarias wrote:

> It adds some extra build time when doing autoreconf passes but the alternative
> would require a new GETTEXTIZE option and package audit which could take some
> time to get resolved.

I believe I would actually prefer a separate GETTEXTIZE option, I'm a
little bit worried about the extra build time. What do others think?

Thanks,

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

  reply	other threads:[~2014-07-14 11:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 17:27 [Buildroot] [PATCH 1/3] gettext: add gettextize definition Gustavo Zacarias
2014-07-12 17:27 ` [Buildroot] [PATCH 2/3] infra: add gettextize run in AUTORECONF Gustavo Zacarias
2014-07-14 11:01   ` Thomas Petazzoni [this message]
2014-07-14 11:04     ` Gustavo Zacarias
2014-07-14 11:07     ` Gustavo Zacarias
2014-07-14 12:30     ` Yann E. MORIN
2014-07-14 12:40       ` Gustavo Zacarias
2014-07-14 12:47         ` Yann E. MORIN
2014-07-14 12:51           ` Gustavo Zacarias
2014-07-14 16:30     ` Arnout Vandecappelle
2014-07-14 19:23       ` Thomas Petazzoni
2014-07-15 13:44         ` Gustavo Zacarias
     [not found]         ` <53C52F0D.70004@zacarias.com.ar>
     [not found]           ` <20140715191515.160512e4@free-electrons.com>
     [not found]             ` <53C562F6.8080705@zacarias.com.ar>
2014-07-15 17:25               ` Gustavo Zacarias
2014-07-12 17:27 ` [Buildroot] [PATCH 3/3] wget: remove redundant gettextize run Gustavo Zacarias
2014-07-13  3:26   ` Baruch Siach

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=20140714130104.480ab4cf@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 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.