Joe Conway wrote: | Scot L. Harris wrote: |> Running Fedora Core 2 trying to build pgadmin3 from source. |> |> Build wxWindows from sources. Appeared to build and install no problem. |> |> But when building pgadmin get the following error as it tries to build |> pgadmin3. |> |> /usr/local/lib/libwx_gtk2ud_core-2.5.a(corelib_settings.o)(.text+0xa55): |> In function `wxSystemSettingsNative::GetFont(wxSystemFont)': |> src/gtk/settings.cpp:346: undefined reference to |> `_gtk_rc_context_get_default_font_name' |> /usr/local/lib/libwx_gtk2ud_core-2.5.a(corelib_menu.o)(.text+0xc5c): In |> function `wxMenubarUnsetInvokingWindow': |> src/gtk/menu.cpp:275: undefined reference to `_gtk_accel_group_detach'
| | After lots of googling I found reference to the fact that wxWindows uses | gtk functions that are supposed to be internal use only (i.e. all the | _gtk* functions). The version of gtk that ships with fc2 no longer | exports these symbols. My solution was to patch gtk to re-allow export | of the internal symbols -- see attached patch.
Would it be better for us to put a patch into our wxWindows tree for this, rather than patching gtk? Do we really want to maintain a gtk patch as well?
Perhaps, but I have no idea what the implications are for wxWindows if you remove the _gtk* calls. I really didn't want to take the time myself to evaluate it. Clearly that is what needs to happen in the long run though.
Also, I've built pgAdmin3 on a fresh FC2 without having to patch
anything, which means that there are probably changes in the wxWindows tree to fix this. Perhaps we can backport them?
Not sure. My attempts were also on a fresh FC2 install, and I had the problem as described by Scot.
Joe
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
