Menu
▾
▴
gnuplot-beta
|
From: Mojca M. <moj...@gm...> - 2012-08-26 14:20:55
|
Hello, I just realized that I don't get any labels with wxt terminal under Mac OS X (neither with 2.8 nor with 2.9.4). Is there any other mac user out there who ever tried to use wxt? It is possible that some recent library changes under MacPorts broke the functionality. I have no idea what exactly is going on. If I try to change the font, it crashes with (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (process:3664): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed (process:3664): GLib-GObject-CRITICAL **: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-CRITICAL **: void pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed (process:3664): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderCoreText', script='common' (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (process:3664): Pango-WARNING **: couldn't load font "Lucida Not-Rotated 320", modified variant/weight/stretch as fallback, expect ugly output. (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (process:3664): Pango-ERROR **: Could not load fallback font, bailing out. Trace/BPT trap: 5 Does anyone have any idea what could be going on? Mojca |
|
From: Daniel J S. <dan...@ie...> - 2012-08-27 19:44:23
|
On 08/26/2012 09:20 AM, Mojca Miklavec wrote: > Hello, > > I just realized that I don't get any labels with wxt terminal under > Mac OS X (neither with 2.8 nor with 2.9.4). Is there any other mac > user out there who ever tried to use wxt? > > It is possible that some recent library changes under MacPorts broke > the functionality. That would be my guess judging from what you've reported. I've little knowledge of MacPorts, but it appears that wxt is attempting to call all these global functions which then get lost somewhere or in some way. You recompiled with a proper configuration from scratch, i.e., ./prepare, ./configure? That should find the proper header files, but you may want to check that is in fact the case. Dan > I have no idea what exactly is going on. If I try > to change the font, it crashes with > > (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > > (process:3664): GLib-GObject-CRITICAL **: g_object_get_qdata: > assertion `G_IS_OBJECT (object)' failed > > (process:3664): GLib-GObject-CRITICAL **: g_object_set_qdata_full: > assertion `G_IS_OBJECT (object)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-CRITICAL **: void > pango_fontset_foreach(PangoFontset *, PangoFontsetForeachFunc, > gpointer): assertion `PANGO_IS_FONTSET (fontset)' failed > > (process:3664): Pango-WARNING **: failed to choose a font, expect ugly > output. engine-type='PangoRenderCoreText', script='common' > > (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > > (process:3664): Pango-WARNING **: couldn't load font "Lucida > Not-Rotated 320", modified variant/weight/stretch as fallback, expect > ugly output. > > (process:3664): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > > (process:3664): Pango-ERROR **: Could not load fallback font, bailing out. > Trace/BPT trap: 5 > > Does anyone have any idea what could be going on? > > Mojca > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta > -- Dan Sebald email: daniel(DOT)sebald(AT)ieee(DOT)org URL: http://www(DOT)dansebald(DOT)com |
|
From: Mojca M. <moj...@gm...> - 2012-08-27 21:02:25
|
On Mon, Aug 27, 2012 at 9:44 PM, Daniel J Sebald wrote: > On 08/26/2012 09:20 AM, Mojca Miklavec wrote: >> >> Hello, >> >> I just realized that I don't get any labels with wxt terminal under >> Mac OS X (neither with 2.8 nor with 2.9.4). Is there any other mac >> user out there who ever tried to use wxt? >> >> It is possible that some recent library changes under MacPorts broke >> the functionality. > > That would be my guess judging from what you've reported. I've little > knowledge of MacPorts, but it appears that wxt is attempting to call all > these global functions which then get lost somewhere or in some way. > > You recompiled with a proper configuration from scratch, i.e., ./prepare, > ./configure? I tried two scenarios: - slightly patched 4.6 (with more-or-less original ./configure file; I'm saying "more-or-less" because of a bug in autotools that had to be fixed, and the patches that were needed to compile Qt) - latest CVS version with ./prepare, ./configure, ... I also tried with wxWidgets: - 2.8 - 2.9.4 - 2.9.5 and they all resulted in the same behaviour. I didn't try to change the version of pango/cairo/anyotherlib. > That should find the proper header files, but you may want to > check that is in fact the case. What exactly should I look for? Mojca |
|
From: Daniel J S. <dan...@ie...> - 2012-08-27 21:13:47
|
On 08/27/2012 04:02 PM, Mojca Miklavec wrote: > On Mon, Aug 27, 2012 at 9:44 PM, Daniel J Sebald wrote: >> On 08/26/2012 09:20 AM, Mojca Miklavec wrote: >>> >>> Hello, >>> >>> I just realized that I don't get any labels with wxt terminal under >>> Mac OS X (neither with 2.8 nor with 2.9.4). Is there any other mac >>> user out there who ever tried to use wxt? >>> >>> It is possible that some recent library changes under MacPorts broke >>> the functionality. >> >> That would be my guess judging from what you've reported. I've little >> knowledge of MacPorts, but it appears that wxt is attempting to call all >> these global functions which then get lost somewhere or in some way. >> >> You recompiled with a proper configuration from scratch, i.e., ./prepare, >> ./configure? > > I tried two scenarios: > - slightly patched 4.6 (with more-or-less original ./configure file; > I'm saying "more-or-less" because of a bug in autotools that had to be > fixed, and the patches that were needed to compile Qt) > - latest CVS version with ./prepare, ./configure, ... > > I also tried with wxWidgets: > - 2.8 > - 2.9.4 > - 2.9.5 > and they all resulted in the same behaviour. I didn't try to change > the version of pango/cairo/anyotherlib. > >> That should find the proper header files, but you may want to >> check that is in fact the case. > > What exactly should I look for? When the actual compile commands appear on the screen during "make", check where the -I directories point to and that the header files in that directory(ies) agree with the library(ies) eventually being linked to. If there is some slight mismatch between those two, the routines will be found and run but behave erratically. Dan |
|
From: Mojca M. <moj...@gm...> - 2012-08-27 21:38:52
|
On Mon, Aug 27, 2012 at 11:13 PM, Daniel J Sebald wrote: > On 08/27/2012 04:02 PM, Mojca Miklavec wrote: >> >>> That should find the proper header files, but you may want to >>> check that is in fact the case. >> >> >> What exactly should I look for? > > > When the actual compile commands appear on the screen during "make", check > where the -I directories point to and that the header files in that > directory(ies) agree with the library(ies) eventually being linked to. If > there is some slight mismatch between those two, the routines will be found > and run but behave erratically. It looks correct to me (duplicates removed): -L/opt/local/lib -lz -lpangocairo-1.0 -lcairo -lpangoft2-1.0 -lpango-1.0 -lm -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lintl -framework Cocoa -I/opt/local/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng14 -I/opt/local/include/pango-1.0 -I/opt/local/include/cairo -I/opt/local/include/QtCore -I/opt/local/include/QtGui -I/opt/local/include/QtNetwork -I/opt/local/include/QtSvg Is there any function to check? Mojca |
|
From: Daniel J S. <dan...@ie...> - 2012-08-27 22:19:54
|
On 08/27/2012 04:38 PM, Mojca Miklavec wrote: > On Mon, Aug 27, 2012 at 11:13 PM, Daniel J Sebald wrote: >> On 08/27/2012 04:02 PM, Mojca Miklavec wrote: >>> >>>> That should find the proper header files, but you may want to >>>> check that is in fact the case. >>> >>> >>> What exactly should I look for? >> >> >> When the actual compile commands appear on the screen during "make", check >> where the -I directories point to and that the header files in that >> directory(ies) agree with the library(ies) eventually being linked to. If >> there is some slight mismatch between those two, the routines will be found >> and run but behave erratically. > > It looks correct to me (duplicates removed): > > -L/opt/local/lib -lz -lpangocairo-1.0 -lcairo -lpangoft2-1.0 > -lpango-1.0 -lm -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 > -lintl -framework Cocoa > > -I/opt/local/include -I/opt/local/include/glib-2.0 > -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 > -I/opt/local/include/freetype2 -I/opt/local/include/libpng14 > -I/opt/local/include/pango-1.0 -I/opt/local/include/cairo > -I/opt/local/include/QtCore -I/opt/local/include/QtGui > -I/opt/local/include/QtNetwork -I/opt/local/include/QtSvg > > Is there any function to check? Not sure. You are seeing both glib errors and pango errors. glib-2.0 looks consistent. As for pango, is there a difference between "pangocairo-1.0" and "pango-1.0", or is there some header file withing "pango-1.0" that addresses that? If you can create a Qt terminal plot using a command that doesn't have labels or text, then I would assume Qt headers/library match. I do see one small discrepancy. The header file indicates "freetype2", while the library linked in is "freetype" without the 2. Now, if there is a different library "-lfreetype2" that can be linked to, that might be where the problem resides, i.e., slightly different font definitions with a different number of descriptive variables. (I know little about Windows freetype.) I don't see how that would account for the glib errors though. Anyway, look into that: freetype2 vs. freetype library. Dan |
