Re: [Slackbuilds-users] VirtualBox
On Fri, 2008-09-26 at 08:00:16 -0400, [EMAIL PROTECTED] wrote: > On Friday 26 September 2008 06:09:55 Audrius Kažukauskas wrote: > > and I've built VBox with > > VBOXUSERS=no QT4=yes QT3=no flags. > > If you use QT3=no it effectively disables QT4 also, > as you can see from this bit of code from the SlackBuild. > > #<--- if no QT3 jump down to the last else > if [ "$QT3" = "yes" ]; then > qt3gui="--with-qt-dir=/usr/lib/qt" > > if [ "$QT4" = "yes" ]; then > patch -d src/VBox/Installer/linux -i $CWD/VBox.diff > qt4gui="--with-qt4-dir=/usr/lib/qt4" > GUI="VirtualBox VirtualBox3" > else > cd src/VBox/Installer/linux > sed -i "s|/VirtualBox|/VirtualBox3|" VBox.sh > cd - > qt4gui="--disable-qt4" > GUI="VirtualBox" > fi > #<- last else way down here > else > qt3gui="--disable-qt3" > fi > > QT4=yes QT3=yes should make things work as you expected. That was it! Since I don't have Qt3, I previously thought it would be good idea to explicitly tell the build script what I have and what I don't. But it seems that telling QT3=no is meant to disable GUI at all (for headless environments). In my case Qt4 GUI is still built, it's just that GUI variable is not set in the SlackBuild, hence the missing VirtualBox symlink. I done some quick edits to the script, rebuilt, and now I can start VirtualBox from command line or KMenu. Thanks David and Heinz for the help! -- Audrius Kažukauskas pgpmhodIX4qow.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
[EMAIL PROTECTED] wrote: > On Friday 26 September 2008 08:18:48 Heinz Wiesinger wrote: >> I just found a bug in the SlackBuild regarding only building qt4 interface, >> and the required symlink is just not created in that case too. So there are >> even two bugs now :( > > This is what I meant by "it effectively disables QT4 also" I was referring to > the code in the SlackBuild. The symlinks are never created because the whole > QT4 section is bypassed. > ___ I thought you had to specify building FOR QT4 when running the build script... hrm.. I'm debating upgrading to the packages in /testing.. maybe I'll give it a shot some time today if I have time. -Matt ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
On Friday 26 September 2008 08:18:48 Heinz Wiesinger wrote: > I just found a bug in the SlackBuild regarding only building qt4 interface, > and the required symlink is just not created in that case too. So there are > even two bugs now :( This is what I meant by "it effectively disables QT4 also" I was referring to the code in the SlackBuild. The symlinks are never created because the whole QT4 section is bypassed. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
Am Freitag, 26. September 2008 13:53:49 schrieb Audrius Kažukauskas: > On Fri, 2008-09-26 at 13:32:29 +0200, Heinz Wiesinger wrote: > > > I think menu entry is missing probably due to non-existent VirtualBox > > > executable in $PATH. > > > > nope. kde looks for .desktop files in certain directories, in this > > case /usr/share/applications/ > > I understand that, but VirtualBox.desktop points to VirtualBox and since > it is missing, maybe KDE4 just ignores the menu entry (not that I know > this for sure...). This might be > > > No /usr/bin/VirtualBox. /usr/bin/VBox exists, but trying to run it > > > gives me "Unknown application - VBox" output. > > > > This and the menu problems leaves the assumption that doinst.sh didn't > > get executed on installation. Further symptoms could be non-existent > > VBoxManage, VBoxSDL, VBoxHeadless and some more in /usr/bin. > > $ VBox > VBox VBoxDeleteIF VBoxManageVBoxTap VBoxVRDP > VBoxAddIF VBoxHeadless VBoxSDL VBoxTunctl > > Running some of those (for example VBoxManage) outputs version and usage > information, so here everything looks fine. Alright. I have the following lines in my doinst.sh: ( cd usr/bin ; rm -rf VirtualBox ) ( cd usr/bin ; ln -sf /usr/bin/VBox VirtualBox ) The quick fix should be to just create the symlink to /usr/bin/VBox as in the lines above. I just found a bug in the SlackBuild regarding only building qt4 interface, and the required symlink is just not created in that case too. So there are even two bugs now :( Thanks for the report, I'll resolve this as soon as possible. Grs, Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
[EMAIL PROTECTED] wrote: > On Friday 26 September 2008 06:09:55 Audrius Kažukauskas wrote: > > and I've built VBox with > > VBOXUSERS=no QT4=yes QT3=no flags. > > If you use QT3=no it effectively disables QT4 also, > as you can see from this bit of code from the SlackBuild. > > #<--- if no QT3 jump down to the last else > if [ "$QT3" = "yes" ]; then > qt3gui="--with-qt-dir=/usr/lib/qt" > > if [ "$QT4" = "yes" ]; then > patch -d src/VBox/Installer/linux -i $CWD/VBox.diff > qt4gui="--with-qt4-dir=/usr/lib/qt4" > GUI="VirtualBox VirtualBox3" > else > cd src/VBox/Installer/linux > sed -i "s|/VirtualBox|/VirtualBox3|" VBox.sh > cd - > qt4gui="--disable-qt4" > GUI="VirtualBox" > fi > #<- last else way down here > else > qt3gui="--disable-qt3" > fi > > QT4=yes QT3=yes should make things work as you expected. Well, no. VirtualBox's configure has a weird behaviour regarding qt. It does not find qt3 automatically, even though it searches the right paths, so I have to specify the qt3-install-directory with --with-qt-dir. For some reason, if I use that method it does then not find qt4 either, which is why I have to use a similar method for qt4 too. However, if only qt4 is requested, configure has no problems with finding it automatically. Unfortunately this reveals a bug I haven't thought of before, as one can't disable both qt3 and qt4 at the same time. I will resolve this as soon as possible. Grs, Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
On Friday 26 September 2008 06:09:55 Audrius Kažukauskas wrote: > and I've built VBox with > VBOXUSERS=no QT4=yes QT3=no flags. If you use QT3=no it effectively disables QT4 also, as you can see from this bit of code from the SlackBuild. #<--- if no QT3 jump down to the last else if [ "$QT3" = "yes" ]; then qt3gui="--with-qt-dir=/usr/lib/qt" if [ "$QT4" = "yes" ]; then patch -d src/VBox/Installer/linux -i $CWD/VBox.diff qt4gui="--with-qt4-dir=/usr/lib/qt4" GUI="VirtualBox VirtualBox3" else cd src/VBox/Installer/linux sed -i "s|/VirtualBox|/VirtualBox3|" VBox.sh cd - qt4gui="--disable-qt4" GUI="VirtualBox" fi #<- last else way down here else qt3gui="--disable-qt3" fi QT4=yes QT3=yes should make things work as you expected. David Somero ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
On Fri, 2008-09-26 at 13:32:29 +0200, Heinz Wiesinger wrote: > > I think menu entry is missing probably due to non-existent VirtualBox > > executable in $PATH. > > nope. kde looks for .desktop files in certain directories, in this > case /usr/share/applications/ I understand that, but VirtualBox.desktop points to VirtualBox and since it is missing, maybe KDE4 just ignores the menu entry (not that I know this for sure...). > > No /usr/bin/VirtualBox. /usr/bin/VBox exists, but trying to run it > > gives me "Unknown application - VBox" output. > > This and the menu problems leaves the assumption that doinst.sh didn't get > executed on installation. Further symptoms could be non-existent VBoxManage, > VBoxSDL, VBoxHeadless and some more in /usr/bin. $ VBox VBox VBoxDeleteIF VBoxManageVBoxTap VBoxVRDP VBoxAddIF VBoxHeadless VBoxSDL VBoxTunctl Running some of those (for example VBoxManage) outputs version and usage information, so here everything looks fine. > If that is the case there is the question why it didn't get executed. Have > you > installed it with install-/upgradepkg? I installed it with upgradepkg over the 2.0.0 (which had the same symptoms, but I just hadn't free time to figure things out and assumed that it may be a problem with 2.0.0 version). > You could maybe try reinstalling the same package and look if doinst.sh gets > executed. Tried upgradepkg --reinstall. It's still the same. -- Audrius Kažukauskas pgpDOsniNKscv.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
Audrius Kažukauskas wrote: > On Fri, 2008-09-26 at 12:48:28 +0200, Heinz Wiesinger wrote: > > This seems strange. I can't tell about the menu-thing, as I don't have > > the time to build virtualbox on current at the moment, but you should be > > able to start virtualbox via command-line by typing "VirtualBox". > > I think menu entry is missing probably due to non-existent VirtualBox > executable in $PATH. nope. kde looks for .desktop files in certain directories, in this case /usr/share/applications/ > > Things you can check: > > -) Is there a /etc/vbox/vbox.conf.new? If yes, replace it with the old > > one. > > There's only a /etc/vbox/vbox.conf with following content: > > # VirtualBox installation directory > INSTALL_DIR="/usr/lib/virtualbox" > > # vboxdrv source location > MODULE_SRC="/usr/src" This is correct > > -) Is there a /usr/bin/VirtualBox and/or /usr/bin/VBox? > > No /usr/bin/VirtualBox. /usr/bin/VBox exists, but trying to run it > gives me "Unknown application - VBox" output. This and the menu problems leaves the assumption that doinst.sh didn't get executed on installation. Further symptoms could be non-existent VBoxManage, VBoxSDL, VBoxHeadless and some more in /usr/bin. If that is the case there is the question why it didn't get executed. Have you installed it with install-/upgradepkg? You could maybe try reinstalling the same package and look if doinst.sh gets executed. Grs, Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
On Fri, 2008-09-26 at 12:48:28 +0200, Heinz Wiesinger wrote: > This seems strange. I can't tell about the menu-thing, as I don't have the > time to build virtualbox on current at the moment, but you should be able to > start virtualbox via command-line by typing "VirtualBox". I think menu entry is missing probably due to non-existent VirtualBox executable in $PATH. > Things you can check: > -) Is there a /etc/vbox/vbox.conf.new? If yes, replace it with the old one. There's only a /etc/vbox/vbox.conf with following content: # VirtualBox installation directory INSTALL_DIR="/usr/lib/virtualbox" # vboxdrv source location MODULE_SRC="/usr/src" > -) Is there a /usr/bin/VirtualBox and/or /usr/bin/VBox? No /usr/bin/VirtualBox. /usr/bin/VBox exists, but trying to run it gives me "Unknown application - VBox" output. > Having the binaries in /usr/lib/virtualbox is indeed not perfect, but > currently it is along the lines of other distributions. I will eventually try > to move them directly into /usr/bin, but this will not be easy and I don't > know if it is possible at all. -- Audrius Kažukauskas pgpTJHf4XasF5.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] VirtualBox
Audrius Kažukauskas wrote: > Hello, > > I am using KDE 4.1.1 from -current and VirtualBox 2.0.2 which I've built > using a SlackBuild from SBo, and there's no menu entry for it in KMenu > (or whatever it's called right now), neither I can run it by typing > `VirtualBox' in command line. The only way to run it is to type a full > path to /usr/lib/virtualbox/VirtualBox (BTW, it's a bit strange place > for the executable file). If I remember correctly, there was no such > problem with KDE3 and VirtualBox 1.6.x. I understand that SBo scripts > are meant to use in -stable, but still this seems wrong. Is it just me > or is it a problem of VirtualBox itself? Oh, and I've built VBox with > VBOXUSERS=no QT4=yes QT3=no flags. This seems strange. I can't tell about the menu-thing, as I don't have the time to build virtualbox on current at the moment, but you should be able to start virtualbox via command-line by typing "VirtualBox". Things you can check: -) Is there a /etc/vbox/vbox.conf.new? If yes, replace it with the old one. -) Is there a /usr/bin/VirtualBox and/or /usr/bin/VBox? Having the binaries in /usr/lib/virtualbox is indeed not perfect, but currently it is along the lines of other distributions. I will eventually try to move them directly into /usr/bin, but this will not be easy and I don't know if it is possible at all. Grs Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] VirtualBox
Hello, I am using KDE 4.1.1 from -current and VirtualBox 2.0.2 which I've built using a SlackBuild from SBo, and there's no menu entry for it in KMenu (or whatever it's called right now), neither I can run it by typing `VirtualBox' in command line. The only way to run it is to type a full path to /usr/lib/virtualbox/VirtualBox (BTW, it's a bit strange place for the executable file). If I remember correctly, there was no such problem with KDE3 and VirtualBox 1.6.x. I understand that SBo scripts are meant to use in -stable, but still this seems wrong. Is it just me or is it a problem of VirtualBox itself? Oh, and I've built VBox with VBOXUSERS=no QT4=yes QT3=no flags. -- Audrius Kažukauskas pgpFFpWuaAg3U.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
