SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
All dependencies are installed, but this keeps failing. It is somewhere in the dependency tree for vbam. I am wondering if this is the cause. It builds fine on multilib, but not on pure 64. Can anyone else build it on non-multilib 64?
EDIT: The error is quite abrupt, too:
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with processed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [widget.lo] Error 1
make: Leaving directory `/tmp/SBo/gtkmm-2.24.2/gtk/gtkmm'
make: *** [all-recursive] Error 1
make: Leaving directory `/tmp/SBo/gtkmm-2.24.2/'
make: *** [all] Error 2
gtkmm builds fine on pure 64 bit. It might be an out of ram error.
I can get wxvbam to compile with WxGTK after editing the SlackBuild to have an extra --enable-graphics_ctx at the configure stage and also modifying the vbam CMakeLists.txt but I'm instantly met with a segmentation fault upon running.
Just out of curiosity, what window managers/desktop environments are you all using? It's strange that I can get gvbam working both for 32 and 64 bit. It also makes it rather difficult to fix.
I could probably look into a patch to remove the recent games menu but I don't know if that'll fix the problem.
I think the problem is a combination of the theme icons and the gtk recentmanager fallback.
If gtkRecentManager cannot load "text-x-generic" icon files when it does not know the file mime type it will reach a g_assert in the code which fails and the application dies. I think the vbam code does not attempt to work around this but it's not really their fault.
Fluxbox doesn't set up gtk themes for you so unless you do so gtk applications will use the fallback icon theme which is probably gnome-icon-theme. I'm not sure about KDE and Xfce, but I'm guessing some of the themes you can choose probably don't have text-x-generic icons in them.
EDIT: Well, can't get xfce to work even choosing gnome or tango icons so probably some other settings also matter. gtk fallback icons might be something else. I will probably stop digging.