From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] host-gettext build failure (emacs dependency?)
Date: Thu, 1 Aug 2013 16:31:25 +0200 [thread overview]
Message-ID: <20130801163125.142e2fce@skate> (raw)
In-Reply-To: <CAAXf6LVsJ6uZbeiRPHcru+Q0J8J2+Xn5ixsTCe4LNZpOm1e67Q@mail.gmail.com>
Dear Thomas De Schampheleire,
On Thu, 1 Aug 2013 15:58:06 +0200, Thomas De Schampheleire wrote:
> But more generally, I wonder why host-gettext needs/uses emacs at all.
> The target gettext already disables several things:
> GETTEXT_CONF_OPT += \
> --disable-libasprintf \
> --disable-acl \
> --disable-openmp \
> --disable-rpath \
> --disable-java \
> --disable-native-java \
> --disable-csharp \
> --disable-relocatable \
> --without-emacs
>
> but the host-gettext seems to be full. Do we really need e.g. emacs
> support for host-gettext? What about csharp, java, native-java?
Hum:
HOST_GETTEXT_CONF_OPT = \
--disable-libasprintf \
--disable-acl \
--disable-openmp \
--disable-rpath \
--disable-java \
--disable-native-java \
--disable-csharp \
--disable-relocatable \
--without-emacs
So we also disable Emacs support and lots of other stuff.
I guess you don't have 0d4133edfedd8ca641db39d3eec9dc7146c8fa4e, which
has been merged post 2013.05.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-01 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 13:58 [Buildroot] host-gettext build failure (emacs dependency?) Thomas De Schampheleire
2013-08-01 14:31 ` Thomas Petazzoni [this message]
2013-08-01 15:40 ` Thomas De Schampheleire
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=20130801163125.142e2fce@skate \
--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