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] libintl.h: need a hint or two
Date: Mon, 17 May 2010 08:55:20 +0200	[thread overview]
Message-ID: <20100517085520.586c2c8d@surf> (raw)
In-Reply-To: <4BF06BBD.4020908@unix-beratung.de>

On Mon, 17 May 2010 00:03:41 +0200
Robert Urban <urban@unix-beratung.de> wrote:

> I'm trying to build a router/firewall system.  Thus I've chosen the ipsec-tools
> and radvd packages.
> 
> These in turn have a dependency on flex.  The flex compile is failing with the
> following error, when compiling "dfa.c":
> 
> In file included from flexdef.h:102,
>                  from ccl.c:34:
> gettext.h:26:22: error: libintl.h: No such file or directory
> 
> And it's right, there is no "libintl.h" under .../staging/usr/include/...
> 
> Please correct me if I'm wrong, but it seems I can only get libintl.h by turning
> on first UCLIBC_MJN3_ONLY and then UCLIBC_HAS_GETTEXT_AWARENESS, but if
> UCLIBC_MJN3_ONLY is enabled, I get slews of other errors...
> 
> I guess I'm doing something wrong.  Can someone help?

Do you have the full build log available somewhere and the .config file
you are using ?

In general, when using a uClibc toolchain, gettext/libintl must be
compiled separatly from the C library by using the BR2_PACKAGE_GETTEXT
package of Buildroot. So, either flex should depend on it, or it's
because the configure cache has been loaded with incorrect
informations. Only the full build log can tell.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-05-17  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-16 22:03 [Buildroot] libintl.h: need a hint or two Robert Urban
2010-05-17  6:55 ` Thomas Petazzoni [this message]
2010-05-17 10:20   ` Robert Urban
2010-05-17 14:22     ` Robert Urban

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=20100517085520.586c2c8d@surf \
    --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