Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Bergmann <bergmann@rosho.de>
To: buildroot@busybox.net
Subject: [Buildroot] running gtk programs fail
Date: Fri, 08 Nov 2013 15:09:51 +0100	[thread overview]
Message-ID: <527CF0AF.5070306@rosho.de> (raw)
In-Reply-To: <20131108111148.640ce383@skate>

Am 08.11.2013 11:11, schrieb Thomas Petazzoni:
> Dear Frank Bergmann,
>
> On Fri, 08 Nov 2013 11:08:49 +0100, Frank Bergmann wrote:
>
>>> Did I miss something or is libgtk broken ?
>>
>> I did a step down and wrote a small glib program (in attachment). But
>> it does not work in buildroot-2013.08.1 ! The glib main loop seems to
>> get no events from timer nor from input source. On my host system the
>> program works with no issues.
>>
>> Can anybody verify this behaviour or have a working example for me ?
>>
>> In attachment I send the source of the test program and my buildroot
>> config.
>
> Are you testing against uClibc? If so, can you test against (e)glibc?

I tested against (out-of-the-box selected) uClibc.

So as you suggested I tested against eglibc and it seems to work. I also 
did a test against buildroot git-repository. The git version seems also 
to work even with uClibc. It has the same version of uClibc but more 
patches than 2013.08.1. So I guess one (or more) of these patches make 
glib2 happy.

Thanks,
Frank.

  reply	other threads:[~2013-11-08 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 12:54 [Buildroot] running gtk programs fail Frank Bergmann
2013-09-14  5:35 ` Thomas Petazzoni
2013-09-16 15:34   ` Frank Bergmann
2013-11-08 10:08 ` Frank Bergmann
2013-11-08 10:11   ` Thomas Petazzoni
2013-11-08 14:09     ` Frank Bergmann [this message]
2013-11-08 12:26   ` Peter Korsgaard

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=527CF0AF.5070306@rosho.de \
    --to=bergmann@rosho.de \
    --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