Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Zuerker <heiko@zuerker.org>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain and iconv in libglib2.mk
Date: Sat, 4 Dec 2010 13:34:29 -0600	[thread overview]
Message-ID: <004e01cb93ea$44a07d70$cde17850$@zuerker.org> (raw)
In-Reply-To: <1291490772.14151.2488.camel@coalu.atr>

Hey,

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-
> bounces at busybox.net] On Behalf Of Lionel Landwerlin
> Sent: Saturday, December 04, 2010 1:26 PM
> To: buildroot at busybox.net
> Subject: Re: [Buildroot] external toolchain and iconv in libglib2.mk
> 
> Ok great,
> 
> It looks like something is wrong with your host. You do not seem to have
> libiconv.so on your system, but still your /usr/include/iconv.h defines a
> _LIBICONV_H.

Libiconv.so is there
 
> So you might have a libc compiled with iconv support, but you're using
> libiconv's header, that is strange...

Yes that was the issue. I copied iconv.h from glibc and now it works.
 
> Or maybe even more strange, you've got libc with iconv support and on top
> of that you've installed libiconv, which is confusing glib...
> 
> I'm afraid you'll have to fix your system.

No worries, as long as I know what's going on, I can fix it.

Thanks for your quick help!

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org

      reply	other threads:[~2010-12-04 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 17:13 [Buildroot] external toolchain and iconv in libglib2.mk Heiko Zuerker
2010-12-04 17:17 ` Lionel Landwerlin
2010-12-04 17:21   ` Heiko Zuerker
2010-12-04 17:37     ` Lionel Landwerlin
2010-12-04 18:34       ` Heiko Zuerker
2010-12-04 19:26         ` Lionel Landwerlin
2010-12-04 19:34           ` Heiko Zuerker [this message]

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='004e01cb93ea$44a07d70$cde17850$@zuerker.org' \
    --to=heiko@zuerker.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