-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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. | | I could not get gtk+-2.4.0 to build on my system starting from the | (supposedly) fc2 src rpm. So I ended up building a gtk+-2.4.1 rpm using | the patched source as mentioned above. From there, all was well with | pgadmin3.
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? 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?
ahp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows 2000) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA2Ywcf/U4M//FQ/URAgKiAKC4KixjUlGgTebwgZsiFf+lRS5rIACdGZQh jRBCMvZWmTj4vTmJ2XEdt9M= =AdzQ -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly