SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
Code:
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[2]: *** [widget.lo] Error 1
make[2]: Leaving directory `/tmp/SBo/gtkmm-2.24.2/gtk/gtkmm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/gtkmm-2.24.2/'
make: *** [all] Error 2
GTKmm was a dependency for the old GTK based UI. I highly doubt they removed the code for it.
As far as WxWidgets go, you may have to install WxPython or WxGTK to get it working. Not sure though as my luck with that emulator has been hit or miss randomly. Even then I'm at a loss.
Yilez are you building with flagged command "ARCH=x86_64 ./gtkmm.SlackBuild"?
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.
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.
xfce on one laptop, kde on the other. I will give fluxbox a go later (doing processing at the moment. Will take a couple of hours.)
I wasn't passing in any architecture flags to the slackbuild. It isn't something that I've ever had to do and it isn't mentioned on the readme.
RAM might be the problem. I just set up the VM with default RAM. I suppose I should have made sure it was 1 or 2 GB.
If it does build ok in Fluxbox, what does that mean? Are KDE and XFCE knackered? Is Fluxbox somehow more correct? Or broken enough to start working again?
I admit, I used fluxbox on my VM for the first time since 2002. I am liking it more than I ever thought possible. If XFCE and KDE are somehow broken, I might be switching permanently.
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.
So, I can confirm that it works fine in fluxbox on multilib.
I think this mostly rules out the VBAM slackbuild being dodgy. I don't know enough about the gnome-icon-theme or anything else to really help. I rebuilt it the other day, and that didn't help.
By the way, I'm still testing with version 1159. I haven't changed to 1199 at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.