|
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 |