From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] TinyX woes...
Date: Mon, 13 Aug 2007 22:34:55 -0700 (PDT) [thread overview]
Message-ID: <12138977.post@talk.nabble.com> (raw)
In-Reply-To: <46C0C586.9060406@promwad.com>
Hi Ivan
I am also working on ARM on arm926ejs. Since 3 weeks i am finding it too
difficult to get ahead of building libglib2. it stops with error on
libintl.h which is deleted by uclibc. I really want to build a gtk with
buildroot but its to going ahead. i enabled locale & wchar and used
uclinc-9.29.0-wchar.config but it still failed at libglib2 stage. so can u
share ur buildroot config file & uclinc config files and details of any
changes u have done with buildroot. this will really be a gr8 help to me.
also what buildroot version or snapshot did u try.
Regards
Gururaja
Regards
Gururaja
--
View this message in context: http://www.nabble.com/TinyX-woes...-tf4263243.html#a12138977
Sent from the BuildRoot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-08-14 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 20:29 [Buildroot] TinyX woes Ulf Samuelsson
2007-08-13 20:37 ` Ulf Samuelsson
2007-08-13 20:56 ` Ivan Kuten
2007-08-14 5:34 ` Hebbar [this message]
2007-08-14 9:37 ` vano
2007-08-14 12:05 ` Hebbar
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=12138977.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.