Thanks for the replies. I tried loading without the splash screen, and I got the same error. While I test some of the other solutions (different installs for wxWidgets), here's the general procedure I used to install C::B and the various dependencies (unfortunately, due to the sheer number of dependencies I had to install, I forget all the specifics):
1. Download and extract the source code
2a. If it's a standard package, use autogen.sh/bootstrap/aclocal, then ./configure --prefix=$HOME and check for errors. Adjust environment variables, command line options, and install dependencies as necessary until this step proceeds without error.
3a. Run make and make install (and if errors do happen here, check configurations and dependencies. Usually problems were caught at the configuration step, but some didn't show up until here)
4a. Test that it works.
2-4b. For non-standard installs, follow the appropriate instructions, either within the package, or otherwise from a site such as Linux from Scratch.
5. If this is a dependency, go back up and continue trying to install the package that required it.
Here's a list of all the packages I ended up installing:
atk-2.11.1
automake-1.14
cairo-1.12.16
codeblocks_13.12-1
docbook-xml-4.5
docbook-xsl-1.71.1
expat-2.1.0
fontconfig-2.11.0
freetype-2.5.3
gdk-pixbuf-2.30.6
gettext-0.18.3.1
glib-2.38.2
gtk+-2.24.23
harfbuzz-0.9.27
help2man-1.40.4-1-msys-1.0.17-src
hunspell-1.3.2
itstool-2.0.2
libogg-1.3.1
libpng-1.6.10
libtool-2.4
libvorbis-1.3.4
libxml2-2.9.1
libXrender-0.9.8
pango-1.36.3
pixman-0.32.4
pkg-config-0.22
ragel-6.8
renderproto-0.11.1
util-macros-1.18.0
wxWidgets-3.0.0
xextproto-7.3.0
xproto-7.0.25
zlib-1.2.8
...Seriously, sadly. The sunk-cost fallacy really dragged me in to seeing this through to completion. For any IT managers out there, the above list is why "Just install it in your user-space" is not a good reply to an installation request.
I'll post back once I've tried installing C::B with jens' configure options, and with wx2.8, which will take some time to build.
EDIT TO UPDATE:
Okay, installing wx2.8 helped. It now loads up, but I ran into an assert fail while trying to debug code:
ASSERT INFO:
./src/propgrid.cpp(7627): assert "editor" failed in DoSelectProperty(): NULL editor class not allowed
BACKTRACE:
[1] wxPropertyGrid::DoSelectProperty(wxPGProperty*, unsigned int)
[2] wxPropertyGrid::AddToSelectionFromInputEvent(wxPGProperty*, unsigned int, wxMouseEvent*, int)
[3] wxPropertyGrid::HandleMouseClick(int, unsigned int, wxMouseEvent&)
[4] wxPropertyGrid::OnMouseClick(wxMouseEvent&)
[5] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[6] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[7] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[8] wxEvtHandler::ProcessEvent(wxEvent&)
[9] wxWindow::GTKProcessEvent(wxEvent&) cons)
[10] g_closure_invoke()
[11] g_signal_emit_valist()
[12] g_signal_emit()
[13] gtk_propagate_event()
[14] gtk_main_do_event()
[15] g_main_context_dispatch()
[16] g_main_loop_run()
[17] gtk_main()
[18] wxEventLoop::Run()
[19] wxAppBase::MainLoop()
[20] wxAppBase::OnRun()
This happened after inspecting a vector-like class and clicking on some of the member names that appeared in the inspection window. The program didn't crash, so it's usable at least (and I can disable the display of that error). But I'm not sure if I should report this as a bug, or if it's more likely a result of something improper I did in installing it. Thoughts?
