From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/8] Add a BR2_NEEDS_GETTEXT option
Date: Mon, 17 May 2010 09:47:40 +0200 [thread overview]
Message-ID: <87eihb0y1v.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <332ed1e3ae5fa11372d522c9c0d03cc01475866a.1273836748.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Fri, 14 May 2010 13:37:24 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> When using an external toolchain that uses the glibc or eglibc C
Thomas> libraries, compiling a separate gettext and libintl is not needed and
Thomas> is even a source of confusion, causing build failures. These build
Thomas> failures are due to the fact that when libintl is compiled, it
Thomas> replaces the C library libintl.h by its own, which does #define
Thomas> gettext libintl_gettext. Then, when packages want to use gettext,
Thomas> autoconf realize that gettext is available in the C library and
Thomas> therefore do not add -lintl to the LDFLAGS, causing the build failure
Thomas> because the program has been compiled to use libintl_gettext but this
Thomas> function is not available.
Thomas> Therefore, we should use gettext if a uClibc internal toolchain or a
/should use/should only use/
Thomas> +config BR2_NEEDS_GETTEXT
Thomas> + bool
Thomas> + default y if BR2_TOOLCHAIN_BUILDROOT
Thomas> + default y if BR2_TOOLCHAIN_EXTERNAL_UCLIBC
Thomas> + default n if BR2_TOOLCHAIN_EXTERNAL_GLIBC
You don't really need the 'default n' (as that's default), but ok.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-05-17 7:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 11:37 [Buildroot] [pull request] Pull request for branch 2010-05-14-fixes Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 1/8] Add a BR2_NEEDS_GETTEXT option Thomas Petazzoni
2010-05-14 13:21 ` Lionel Landwerlin
2010-05-17 7:47 ` Peter Korsgaard [this message]
2010-05-19 11:33 ` Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 2/8] Make all package using gettext rely on BR2_NEEDS_GETTEXT Thomas Petazzoni
2010-05-17 7:46 ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 3/8] libcap: fix build failure Thomas Petazzoni
2010-05-17 7:49 ` Peter Korsgaard
2010-05-19 11:30 ` Thomas Petazzoni
2010-05-19 11:50 ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 4/8] libcgicc: fix package after autotools infrastructure conversion Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 5/8] ltrace: fix build failure Thomas Petazzoni
2010-05-15 11:19 ` Microbit_Ubuntu
2010-05-19 11:28 ` Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 6/8] gettext: make only available if BR2_NEEDS_GETTEXT is set Thomas Petazzoni
2010-05-14 13:24 ` Lionel Landwerlin
2010-05-14 11:37 ` [Buildroot] [PATCH 7/8] avahi: needs IPv6 Thomas Petazzoni
2010-05-17 7:55 ` Peter Korsgaard
2010-05-17 13:00 ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 8/8] external toolchain: check BR2_INSTALL_LIBSTDCPP Thomas Petazzoni
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=87eihb0y1v.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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