User forums > Using Code::Blocks
Building Code::Blocks: error: ambiguous overload for 'operator[]'
KirkD:
Could there be a difference between wx 2.8.9 (on my failing CentOS install) and 2.8.10 (on the currently working Fedora install)?
Jenna:
--- Quote from: KirkD on December 08, 2009, 09:07:33 pm ---Could there be a difference between wx 2.8.9 (on my failing CentOS install) and 2.8.10 (on the currently working Fedora install)?
--- End quote ---
If I understood correctly:
--- Quote from: KirkD on December 08, 2009, 07:23:39 pm ---I have wxBase 2.8.9 installed as per yum info wx*. I also have wxGTK 2.8.10 and wxGTK-devel 2.8.10 installed.
--- End quote ---
you have wxWidgets 2.8.9 and 2.8.10 mixed. This might cause problems.
I suggest removing 2.8.9 and only using 2.8.10.
I use wxWidgets from rpmforge on my virtual centos 5.4 box (but it's only 32-bit at the moment).
By the way: wxWidgets definitely works on 64-bit linuxes. I use it everyday on my debian machine, without any problems.
KirkD:
--- Quote from: jens on December 08, 2009, 11:35:46 pm ---
you have wxWidgets 2.8.9 and 2.8.10 mixed. This might cause problems.
I suggest removing 2.8.9 and only using 2.8.10.
--- End quote ---
Yes, seems odd. When I install via yum install wxGTK-devel I end up with wxGTK-2.8.10 which has wxBase-2.8.9 as a dependency. Seems off, but that's the nature of it.
At this point it seems clear that there is something wrong with my wx configuration. I've gone through a few iterations of building wx (ansi vs unicode - unicode fixes a few errors, --with-GTK vs. without - GTK fixes a few errors) but I still have a few errors. I've removed all my installs (make uninstall in each directory) and yum erase'd all wx vestiges. I'm actively working on this for wx:
../configure --enable-xrc --enable-monolithic --enable-unicode
Interestingly, on my fresh install of Fedora 12 (running in VirtualBox), the Code::Blocks build went first try, no errors, no dependencies.
-Kirk
Jenna:
If wxGTK-2.8.10 has wxBase-2.8.9 as dependency, something went wrong.
I don't think that this can work properly.
As written before I have wxwidgets from rpmforge (http://wiki.centos.org/AdditionalResources/Repositories/RPMForge) and it works without any such strange errors.
I don't know, whether 64-bit packages are also available fom there, but I think so.
KirkD:
RPMForge is in my repolist and that is where the packages I mentioned are coming from. I just double checked and indeed if I issue
yum install wxGTK-devel
I get wxGTK-devel 2.8.10 along with wxBase 2.8.9. This could be the source of the problem as you mentioned.
Like I said, I removed all traces of wx from my system (packages and my custom builds) and then I went back to rebuild wx as per this page: http://vunh.blogspot.com/2009/05/codeblocks-installation-in-centos.html
wx built fine and I now have it in a custom directory - /opt/wx/2.8 - I can't see that this should matter much. Currently the Code::Blocks build as per:
./configure --with-contrib-plugins=all
make
is cruising along nicely. It has definitely gone further than ever before. Once it finishes - if it finishes - I'll post back here my results.
-Kirk
EDIT: I corrected ./configure --enable-contrib-plugins=all to ./configure --with-contrib-plugins=all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version