Re: CVS woes: wxt fails

[Daniel J S. <dan...@ie...>]

On 11/25/2015 07:48 AM, pl...@pi... wrote:
> On 25/11/15 09:26, Daniel J Sebald wrote:
>> On 11/25/2015 02:39 AM, pl...@pi... wrote:
>>> Hi,
>>>
>>> Building current CVS gnuplot on Fedora 23 x68_64, I found I had to
>>> explicitly give the WXDIR to get it to configure wxt terminal:
>>>
>>> ./configure --prefix=/usr/local --with-qt --with-wx=/usr/libexec/wxGTK3
>>>
>>> It still fails half way throught the wxt stuff:
>>>
>>> <code>
>>>
>>> wxterminal/wxt_gui.cpp:4197:1: warning: ‘virtual void
>>> wxWindowBase::SetInitialBestSize(const wxSize&)’ is deprecated: use
>>> SetInitialSize() instead. [-Wdeprecated-declarations]
>>> }
>>> ^
>>> In file included from /usr/include/wx-3.0/wx/wx.h:38:0,
>>> from wxterminal/wxt_gui.h:77,
>>> from wxterminal/wxt_gui.cpp:97:
>>> /usr/include/wx-3.0/wx/window.h:1872:13: note: declared here
>>> inline void wxWindowBase::SetInitialBestSize(const wxSize& size)
>>> ^
>>> Makefile:926: recipe for target 'wxterminal/wxt_gui.o' failed
>>> make[4]: *** [wxterminal/wxt_gui.o] Error 1
>>>
>>> </code>
>>>
>>>
>>> There is a raft ( hundreds ) of such deprecation warnings that make it
>>> difficult to find the original error.
>>>
>>> Is there a way to turn off these warnings so that I can see what is
>>> going wrong?
>>
>> Sometimes the warnings and errors go to separate streams, e.g., stdout
>> vs. stderr. Try redirecting the output of the compilation to file and
>> see if there is anything left behind that looks like an error.
>>
>> Dan
>>
>
> Ah, good idea Dan.
>
> make 2>stderr.log
>
> redirecting stderr to a file and searching for "error" found this. It
> seems it is doing an ungodly mix of gtk2.0 and gtk3.0
>
> ============
>
> In file included from /usr/include/gtk-2.0/gdk/gdkscreen.h:32:0,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from wxterminal/wxt_gui.h:191,
> from wxterminal/wxt_gui.cpp:97:
> /usr/include/gtk-2.0/gdk/gdktypes.h:114:39: error: conflicting
> declaration ‘typ$
> typedef struct _GdkDrawable GdkWindow;
> ^
> In file included from /usr/include/wx-3.0/wx/wxprec.h:12:0,
> from wxterminal/wxt_gui.h:75,
> from wxterminal/wxt_gui.cpp:97:
> /usr/include/wx-3.0/wx/defs.h:3412:31: note: previous declaration as
> ‘typedef s$
> typedef struct _GdkWindow GdkWindow;
> ^
> =============
>
> This is probably since I had to provide it with a WXDIR since it could
> not find it on its own.
>
> However the only wx-config on the system is that which I gave it :
> /usr/libexec/wxGTK3/wx-config
>
> If I don't give it a WXDIR in configure it configures to build without wxt.
>
> Fedora seems to offer some kind of gtk3-gtk2 compatability lib ,
> installing this got a bit further:
>
> Installing:
> compat-wxBase3-gtk2 x86_64 3.0.2-5.1.fc23 fedora 1.1 M
> compat-wxGTK3-gtk2 x86_64 3.0.2-5.1.fc23 fedora 5.4 M
> compat-wxGTK3-gtk2-devel x86_64 3.0.2-5.1.fc23 fedora 1.3 M
> compat-wxGTK3-gtk2-gl x86_64 3.0.2-5.1.fc23 fedora 35 k
> compat-wxGTK3-gtk2-media x86_64 3.0.2-5.1.fc23 fedora 56 k
>
> I still need to tell it where to find wx-config otherwise it builds
> without wxt
>
> ./configure --prefix=/usr/local --without-qt
> --with-wx=/usr/libexec/compat-wxGTK3-gtk2/
>
> Now it seems to fail at the linker stage.
>
> /bin/ld: wxterminal/wxt_gui.o: undefined reference to symbol 'XInitThreads'
> /usr/lib64/libX11.so.6: error adding symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status
> make[4]: *** [gnuplot] Error 1
>
>
> I'm a bit included just to give up on wxt and use qt, but from a
> development point of view I suppose this should work.
>
> I don't think I'm trying to do anything particularly odd-ball here. Any
> suggestions?

No real good ideas here Peter, sorry.  Only that maybe you could look at 
the configuration log and search for the first location where gtk2/3 
appears and perhaps try to modify things through a flag or removing some 
developer library that would cause gnuplot to not use gtk3.

Also, qt is good, but slower on some systems and faster on others.  I 
like both qt and wxt, but I've found quite a few odd bugs in each that I 
haven't had time to investigate.

Dan