From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: oselas@community.pengutronix.de, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [oselas] GTK+ on DirectFB
Date: Thu, 26 Jan 2012 16:45:40 +0100 [thread overview]
Message-ID: <CABDcavZ28Zn1D5dTgm5nyeXRnJHmjtbkNUym-71BqC=vu4gRVQ@mail.gmail.com> (raw)
In-Reply-To: <201201261350.00935.jbe@pengutronix.de>
2012/1/26 Juergen Beisert <jbe@pengutronix.de>:
> Hi Guillermo,
>
> Guillermo Rodriguez Garcia wrote:
>> 2012/1/26 Juergen Beisert <jbe@pengutronix.de>:
>> > Hi Guillermo,
>> >
>> > Guillermo Rodriguez Garcia wrote:
>> >> [...]
>> >> (testgtk:739): Gdk-CRITICAL **: IA__gdk_drawable_set_colormap:
>> >> assertion `cmap == NULL || gdk_drawable_get_depth (drawable) == cmd
>> >> (*) Direct/Thread: Started 'EventBufferFeed' (-1) [MESSAGING
>> >> OTHER/OTHER 0/0] <8388608>...
>> >> (!) [ 739: 0.000] --> Caught signal 11 (at 0x28, invalid address)
>> >> <--
>> >> (!!!) *** WARNING [still objects in 'Window Pool'] *** [object.c:241
>> >> in fusion_object_pool_destroy()] (!!!) *** WARNING [still objects in
>> >> 'Layer Region Pool'] ***
>> >> [object.c:241 in fusion_object_pool_destroy()]
>> >> (!!!) *** WARNING [still objects in 'Layer Context Pool'] ***
>> >> [object.c:241 in fusion_object_pool_destroy()]
>> >> (!!!) *** WARNING [still objects in 'Surface Pool'] ***
>> >> [object.c:241 in fusion_object_pool_destroy()]
>> >> Aborted
>> >>
>> >> Can anyone share any experiences on this?
>> >
>> > Did you re-start with a clean GTK after you switch from Xorg to DirectFB?
>> > Sometimes the package's buildsystem does not re-compile everything after
>> > changing some parameters, so some object files are still compiled for the
>> > previous parameter settings. Just an idea.
>>
>> No, I didn't. I assumed ptxdist would take care.
>
> PTXdist: yes. It calls again the package's configure script with the new
> settings. But sometimes the package's buildsystem is broken and it does not
> re-compile all objects in accordance to the new configuration.
I see.
>
>> I'll give this a shot, rebuilding everything from scratch.
>
> Not everything: a "ptxdist clean gtk" should be enough. This means only the
> gtk package starts from scratch.
(Too late :)
Anyway I rebuilt everything from scratch and the problem persists.
If someone has tested this (GTK with DirectFB target), pointers are welcome.
Thanks,
--
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-01-26 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 10:13 [ptxdist] " Guillermo Rodriguez Garcia
2012-01-26 10:32 ` [ptxdist] [oselas] " Juergen Beisert
2012-01-26 12:31 ` Guillermo Rodriguez Garcia
2012-01-26 12:50 ` Juergen Beisert
2012-01-26 15:45 ` Guillermo Rodriguez Garcia [this message]
2012-01-26 10:35 ` [ptxdist] " Robert Schwebel
2012-01-26 12:40 ` Guillermo Rodriguez Garcia
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='CABDcavZ28Zn1D5dTgm5nyeXRnJHmjtbkNUym-71BqC=vu4gRVQ@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=jbe@pengutronix.de \
--cc=oselas@community.pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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