Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian SCHWARZ <christian.schwarz@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glib2 build problem
Date: Tue, 25 Mar 2008 15:19:58 +0100	[thread overview]
Message-ID: <47E90A0E.6000800@st.com> (raw)
In-Reply-To: <46a136670803250708x7c002b28xb7ba002608228299@mail.gmail.com>

ok thanks, in fact the linker did not find libintl:
  arm-linux-uclibc/bin/ld: cannot find -lintl

Do you have an idea how I can tell the toolchain to look also in 
$(BUILDROOT)/linux-toolchain/include and 
$(BUILDROOT)/linux-toolchain/lib ? If not, I have to copy generated libs 
& header files into the toolchain's own lib/ and include/ dirs.

cheers,
Christian

John Voltz wrote:
> Take a look inside config.log. You can find the compiler error there 
> that caused the configure script to fail. That usually tells a lot about 
> the real problem.
> 
> John
> 
> 
> On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ 
> <christian.schwarz at st.com <mailto:christian.schwarz@st.com>> wrote:
> 
>     Dear all,
> 
>     I encounter a build problem with glib2 for an ARM11 target. The error
>     message is the following:
> 
>     ---------------snip---------------------
>     [...]
>     checking libintl.h usability... yes
>     checking libintl.h presence... yes
>     checking for libintl.h... yes
>     checking for ngettext in libc... no
>     checking for bindtextdomain in -lintl... no
>     checking if -liconv is needed to use gettext...
>     checking for ngettext in -lintl... no
>     configure: error:
>     *** You must have either have gettext support in your C library, or
>     use the
>     *** GNU gettext library.
>     (http://www.gnu.org/software/gettext/gettext.html
>     ---------------------snap-------------------------------------
> 
>     It seems as though I should configure ngettext support in libintl, but I
>     don't know how to do so. Is the alternative rebuilding the uclibc,
>     similar to what has been discussed on the mailing list?:
>     http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html
> 
>     Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for ARM
>     Linux has been built (previously) with buildroot.
> 
>     thanks for any hints,
>     Christian
> 
>     _______________________________________________
>     buildroot mailing list
>     buildroot at uclibc.org <mailto:buildroot@uclibc.org>
>     http://busybox.net/mailman/listinfo/buildroot
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2008-03-25 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 13:36 [Buildroot] Glib2 build problem Christian SCHWARZ
2008-03-25 14:08 ` John Voltz
2008-03-25 14:19   ` Christian SCHWARZ [this message]
2008-03-25 14:38     ` John Voltz
2008-03-25 14:42       ` John Voltz
2008-03-25 14:51         ` Christian SCHWARZ

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=47E90A0E.6000800@st.com \
    --to=christian.schwarz@st.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