eboxy and gcc 3.2

NOTE: there are now RPMs built on Red Hat 9 for RPM-based distros available here. This means you can potentially avoid having to go through the instructions below if the RPMs work for you.

Some users have reported problems setting up eboxy on gcc 3.2-based distributions. The problem seems to be that SDL_gui, the base library which eboxy uses to display its GUI, doesn't compile properly out of the box with gcc 3.2. The binary RPMs of SDL_gui don't work either, since it was built against now old versions of SDL, SDL_ttf and SDL_image. SDL_gui is no longer maintained and I have had no replies in response to my emails to the author on this issue, so I decided to try to tackle it myself. As it turns out, it's not too difficult to fix, but does require that you build SDL_gui from source.

How to do it

  1. Remove any old RPM/source installs of SDL_gui if they are present on your system. rpm -e SDL_gui for the rpm installs, make uninstall in the SDL_gui source directory for source installs. We will need to install SDL_gui from source though, so leave the source directory intact if you still have it.
  2. If you are building SDL_gui from a source directory you have used before, run make clean in there. Otherwise unpack a new copy from SDL_gui-0.10.3.tar.gz (also mirrored here).
  3. Run
    export LDFLAGS=-lstdc++
  4. Run ./configure, make and make install for SDL_gui.
  5. Please use the latest version of eboxy. Versions prior to 0.3.5 will not work.

  6. Change directory into the eboxy source directory (unpack it if you haven't already). Before you run ./configure of eboxy, run
    export CXXFLAGS=-I/usr/local/lib/SDL
    Then you can do the usual ./configure, make and make install and it should work fine.

The above was tested on Mandrake Linux 9.0 and Gentoo 1.4rc3. If you have any problems with the instructions above, please email me.

Back to eboxy page