From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] libglibg2 fails
Date: Fri, 16 Jan 2009 09:49:58 +0100 [thread overview]
Message-ID: <87iqof7hzd.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1232091382.8094.40.camel@aeglos.sweden.atmel.com> (Ulf Samuelsson's message of "Fri\, 16 Jan 2009 08\:36\:22 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> When building libglib2 for both AVR32 and ARM I get the following:
Ulf> ...
Ulf> gconvert.c:55:2: error:
Ulf> #error GNU libiconv not in use but included iconv.h is from libiconv
Ulf> make[5]: *** [gconvert.lo] Fel 1
Ulf> ...
Ulf> make[1]: Leaving directory `<buildroot>/build_avr32/libglib2-2.19.4'
Ulf> ...
Ulf> Is there anyone capable of building libglib2?
I've built it several times around christmas for arm (v4l)
Haven't tried since, so it sounds like recent breakage.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-16 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 7:36 [Buildroot] libglibg2 fails Ulf Samuelsson
2009-01-16 8:49 ` Peter Korsgaard [this message]
2009-01-16 9:42 ` Ulf Samuelsson
2009-01-16 11:07 ` Thomas Lundquist
2009-01-16 20:46 ` Ulf Samuelsson
2009-01-16 9:27 ` Daniel James Laird
2009-01-16 9:28 ` Sven Neumann
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=87iqof7hzd.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