From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <201201261350.00935.jbe@pengutronix.de> References: <201201261132.17940.jbe@pengutronix.de> <201201261350.00935.jbe@pengutronix.de> Date: Thu, 26 Jan 2012 16:45:40 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: Re: [ptxdist] [oselas] GTK+ on DirectFB Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Juergen Beisert Cc: oselas@community.pengutronix.de, ptxdist@pengutronix.de 2012/1/26 Juergen Beisert : > Hi Guillermo, > > Guillermo Rodriguez Garcia wrote: >> 2012/1/26 Juergen Beisert : >> > Hi Guillermo, >> > >> > Guillermo Rodriguez Garcia wrote: >> >> [...] >> >> (testgtk:739): Gdk-CRITICAL **: IA__gdk_drawable_set_colormap: >> >> assertion `cmap =3D=3D NULL || gdk_drawable_get_depth (drawable) =3D= =3D cmd >> >> (*) Direct/Thread: Started 'EventBufferFeed' (-1) [MESSAGING >> >> OTHER/OTHER 0/0] <8388608>... >> >> (!) [ =A0739: =A0 =A00.000] --> Caught signal 11 (at 0x28, invalid ad= dress) >> >> <-- >> >> =A0(!!!) =A0*** WARNING [still objects in 'Window Pool'] *** [object.= c:241 >> >> in fusion_object_pool_destroy()] (!!!) =A0*** WARNING [still objects = in >> >> 'Layer Region Pool'] *** >> >> [object.c:241 in fusion_object_pool_destroy()] >> >> =A0(!!!) =A0*** WARNING [still objects in 'Layer Context Pool'] *** >> >> [object.c:241 in fusion_object_pool_destroy()] >> >> =A0(!!!) =A0*** 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 Direct= FB? >> > Sometimes the package's buildsystem does not re-compile everything aft= er >> > 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 n= ot > 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 t= he > 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