User forums > Help

Installing 17.12 on Linux Mint --wxWidgets problem

(1/3) > >>

rjmoses:
I had been experimenting with CB 13.12 on Linux Mint 18.1 with some success but had encountered a few known bugs. (13.12 was the standard package available on LM 18.1.) I wanted to get up to current on the bug fixes, etc.

I first used Jen's Debian repository to upgrade to 17.12 and encountered the error in wxWidgets:

"Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8),
and wxCore used 3.0 (wchar_t,compiler with C++ ABI 1011,wx containers,compatible with 2.8)."

As far as I can tell, this is a problem within wxWidgets.  This same error also occurs in wxGlade. I could not find a way to get compatible compilations for CB and wxWidgets.  (It might exist, but I just couldn't find one.)

I used the procedure from the post "https://askubuntu.com/questions/1030720/how-to-install-latest-codeblocks-from-tar-xz" and get the error:

"codeblocks: symbol lookup error: codeblocks: undefined symbol: _ZN24IncrementalSelectListDlgD1Ev"

The above problem was eliminated by doing:

apt-get remove --purge codeblocks
apt-get remove --purge libcodeblocks0

then repeating the procedure which took me back to Jen's original error--incompatibility between ABI 1009 and ABI 1010.

AFAIK, this is a problem with wxwidgets, but I can't find a solution.

I have been impressed with the capabilities of CB 13.12 and would like to upgrade, but at this point I am stumped and any suggestions would be greatly appreciated. 

Thank you

BlueHazzard:
You have to try to clean up your system....
Remove all wxWidgets libraries and install the system defaults again. I do not know but jens probably installed some wx2.8 library. But codeblocks works now quite well with wx30 and also linux mint arrives with wx30 by default...
After installing the normal wxWidgets library and removing all codeblocks related stuff (you probably have also to uninstall the contrib-plugin package) you can download the source code and go the normal

--- Code: --- ./bootstrap
 ./configure --prefix=/opt/codeblocks-svn --with-contrib-plugins=all
make
sudo make install
--- End code ---
way to build codeblocks and install it

rjmoses:
No, I haven't done a complete clean up--I have other applications that use wxWidgets, such as audacity and filezilla, and I am concerned about breaking them.

I did try to build CB 17.12 from scratch and ended up with a lot of errors (More than I care to wrestle with!) so I do not consider that a viable resolution at the moment.  I am hoping someone in the community might have more experience with the ABI incompatibility problem in wxWidgets.

Thanks.

sodev:
Install the dev packages of your system wxWidgets and compile CodeBlocks against that (it should do this by default anyway). This way you get rid of your library mismatches which occur because the prebuild packages were built against another wxWidgets version and saves you from building wxWidgets yourself and convince CodeBlocks to use that one (i always forget how to do it, but i think the trick is to supply the path to the wx-config script for your selfbuild wxWidgets).

rjmoses:
Are you suggesting that I build both wxWidgets and CodeBlocks from source?  Wouldn't that open a whole new can of worms and perhaps risk screwing up installed applications that are working? 

I am looking to understand why wxwidgets public libraries are compiler dependent and what can be done to work around it.

Navigation

[0] Message Index

[#] Next page