Re: [Slackbuilds-users] virtualbox slackbuilds

On Friday, 2 February 2024 15:01:41 CET Jim wrote: > All, > > I recently started running the 6.6.12 kernel. All (well, everything I use) > is working except virtualbox-kernel, which won't compile on that kernel. > > Looking on the web, I see the particular problem I'm having has been fixed > in

Re: [Slackbuilds-users] virtualbox slackbuilds

Thanks to both 高文偉 and Giancarlo, with the slackbuilds from mdinslage at github, I had VBox 7.0.14 running in no time. (And thanks to Matt Dinslage as well!) SBO admins and volunteers: if the VBox 6 maintainer is out for a long walkabout, perhaps a regular VBox user would like to get the ones fro

Re: [Slackbuilds-users] virtualbox slackbuilds

Il 02/02/24 15:01, Jim ha scritto: All, I recently started running the 6.6.12 kernel. All (well, everything I use) is working except virtualbox-kernel, which won't compile on that kernel. Looking on the web, I see the particular problem I'm having has been fixed in newer versions of virtualbo

Re: [Slackbuilds-users] virtualbox slackbuilds

Hi Jim, Some others and I have been waiting too, as seen in this thread (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-7-on-slackware-15-a-4175727199/) and this thread (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-kernel-slackbuild-for-6-

[Slackbuilds-users] virtualbox slackbuilds

All, I recently started running the 6.6.12 kernel. All (well, everything I use) is working except virtualbox-kernel, which won't compile on that kernel. Looking on the web, I see the particular problem I'm having has been fixed in newer versions of virtualbox. I see that aside from 6.1.55, ther

Re: [Slackbuilds-users] Virtualbox

On Sat, May 20, 2023 at 22:39 (+0200), Heinz Wiesinger wrote: > On Saturday, 20 May 2023 21:27:23 CEST Jim wrote: >> For anyone who is listening and cares... >> See below >> On Fri, May 19, 2023 at 21:04 (+0800), David O'Shaughnessy wrote: >>> There are some of the maintainer's build scripts he

Re: [Slackbuilds-users] Virtualbox

Hi Heinz, I'm pretty sure the version of VirtualBox on SBo (6.1.34) is borked for some particular Windows version, I had endless problems until I updated to virtualbox-6.1.40 from your repo. I think at a minimum the soon to be EOL(?) 6.x branch should be updated to the latest, just for compatibi

Re: [Slackbuilds-users] Virtualbox

On Saturday, 20 May 2023 21:27:23 CEST Jim wrote: > For anyone who is listening and cares... > > See below > > On Fri, May 19, 2023 at 21:04 (+0800), David O'Shaughnessy wrote: > > I'm not too sure why the maintainer is not pushing an update, probably > > busy? > Probably! > > > There are some o

Re: [Slackbuilds-users] Virtualbox

For anyone who is listening and cares... See below On Fri, May 19, 2023 at 21:04 (+0800), David O'Shaughnessy wrote: > I'm not too sure why the maintainer is not pushing an update, probably busy? Probably! > There are some of the maintainer's build scripts here though that are updated: > https

Re: [Slackbuilds-users] Virtualbox

I'm not too sure why the maintainer is not pushing an update, probably busy? There are some of the maintainer's build scripts here though that are updated: https://repo.liwjatan.org/pprkut/15.0/source/ https://repo.liwjatan.org/pprkut/current/source/ On Thu, 11 May 2023, at 12:13 AM, Jim wrote:

[Slackbuilds-users] Virtualbox

The current SlackBuild is for 6.1.34. 6.1.44 came out in April, but is EOL in December. V 7 is now up to 7.0.8. Does anyone know about any problems with upgrading to a newer version? Thanks. Jim ___ SlackBuilds-users mail

Re: [Slackbuilds-users] virtualbox-kernel-addons fails build with kernel 4.4.172

* On 2019 01 Mar 12:49 -0600, Heinz Wiesinger wrote: > There is a small bug in the script that makes it fail with the 32bit smp > kernel. I didn't have time to fix that yet, but will try to get to it > tomorrow. > > In the meantime, if you want to "hack" it, there is a sed call guarded by a > k

Re: [Slackbuilds-users] virtualbox-kernel-addons fails build with kernel 4.4.172

On Friday, 1 March 2019 19:10:48 CET Nate Bargmann wrote: > * On 2019 01 Mar 11:06 -0600, Matteo Bernardini wrote: > > Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann ha > > scritto: Hi Nate, > > > > are you sure that you are using the latest version of the script? > > > > I'm asking becau

Re: [Slackbuilds-users] virtualbox-kernel-addons fails build with kernel 4.4.172

Well, I verified the latest script is available to sbotools and even forced a download of the source package as well as trying to build the package by directly running the script. All to no avail as the build fails at the same point each time as with my screenshots from my OP. Hope that helps. -

Re: [Slackbuilds-users] virtualbox-kernel-addons fails build with kernel 4.4.172

* On 2019 01 Mar 11:06 -0600, Matteo Bernardini wrote: > Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann ha > scritto: > Hi Nate, > > are you sure that you are using the latest version of the script? > > I'm asking because three weeks ago it has been updated > > https://git.slackbuilds.o

Re: [Slackbuilds-users] virtualbox-kernel-addons fails build with kernel 4.4.172

Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann ha scritto: > > I run a 32 and a 64 bit instance of Slackware 14.2 in VirtualBox for > making sure my Slackbuilds work in as clean of an environment as > possible. A couple of days ago I upgraded the 32 bit VM to the latest > Slackware updates

Re: [Slackbuilds-users] virtualbox drv

Did you also rebuild virtualbox-kernel? (Actually, you only have to rebuild virtualbox-kernel after a kernel upgrade, not virtualbox itself.) Dan On Sat, Jul 01, 2017 at 09:00:58PM +0200, Dimitris Zlatanidis wrote: > After the new kernel 4.4.75 installed and rebuild virtualbox I can't > start vb

[Slackbuilds-users] virtualbox drv

After the new kernel 4.4.75 installed and rebuild virtualbox I can't start vboxdrv, any suggestion ? Thanks -- Dimitris Zlatanidis ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slack

[Slackbuilds-users] virtualbox-addons

It seems missing a file INSTVBoxControl => {C}/out/linux.x86/release/bin/additions/VBoxControl INSTVBoxService => {C}/out/linux.x86/release/bin/additions/VBoxService INSTVBoxClient => {C}/out/linux.x86/release/bin/additions/VBoxClient INSTmount.vboxsf => {C}/out/linux.x86/re

Re: [Slackbuilds-users] VirtualBox 5.x

Hello, 2016-01-20 10:33 Ruben Schuller : > > Before I dive headfirst into this, I'd rather ask. Did someone here > > successfully build VirtualBox 5.0.x on Slackware64 14.1? Any > > pitfalls, caveats, whatever? > > I have built a 5.x version, even without a multilib environment. Its > a bit ago,

Re: [Slackbuilds-users] VirtualBox 5.x

Le 20/01/2016 11:33, Ruben Schuller a écrit : > I have built a 5.x version, even without a multilib environment. Its a bit > ago, but I'll see if i have anything useful when I'm back home. > > So long, Thanks very much. I experimented a bit, and succeeded in building 5.0.14 packages for 14.1 an

Re: [Slackbuilds-users] VirtualBox 5.x

Hi! > Before I dive headfirst into this, I'd rather ask. Did someone here > successfully build VirtualBox 5.0.x on Slackware64 14.1? Any pitfalls, > caveats, whatever? I have built a 5.x version, even without a multilib environment. Its a bit ago, but I'll see if i have anything useful when I'm

Re: [Slackbuilds-users] VirtualBox 5.x (correction)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justs upgraded to 5.0.14 with the .run. OK. - Didier -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBAgAGBQJWn3P1AAoJENUCAu9gwD7qXrcH/AiU2+yEdBFYBVUnDAVU4g2h oD4R0yt6WIR1BL+2BPxaJnIqB4wjV/NUpNQLoQj7YxXjqF8GPuLQZdiFAd5MYAgt vJzMi0E2EFZJfObIbpjD

Re: [Slackbuilds-users] VirtualBox 5.x (correction)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/01/2016 11:25, Didier Spaier wrote: > and pick the "run installer" that fist your $ARCG, else you will > find Should read "that fits your $ARCH", sorry. - Didier -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBAgAGBQJWn2dfAAoJENUCAu9gwD

Re: [Slackbuilds-users] VirtualBox 5.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/01/2016 11:06, Nicolas Kovacs wrote: > Before I dive headfirst into this, I'd rather ask. Did someone > here successfully build VirtualBox 5.0.x on Slackware64 14.1? Any > pitfalls, caveats, whatever? Starting VB to check after having seen your

[Slackbuilds-users] VirtualBox 5.x

Hi, I'm running VirtualBox 4.3.34 on my workstation under Slackware64 14.1. I started from the SlackBuild found on SlackBuilds.org, which builds VirtualBox 4.3.24. I made some minor modifications and upgraded it to the latest minor version. This morning I installed a Slackware -current guest syst

[Slackbuilds-users] virtualbox-kernel

Hi! virtualbox-kernel failed to build with the new kernel 4.1.6 ... I have included a patch to build against new kernel if ! [ "${HARDENING:-yes}" = "yes" ]; then sed -i "s/ -DVBOX_WITH_HARDENING//g" \ {vboxdrv,vboxnetadp,vboxnetflt,vboxpci}/Makefile fi + patch -p1 < $CWD/VBoxPci-linux.c.pat

Re: [Slackbuilds-users] virtualbox-kernel: small typo in slack-desc

Le 12/04/2015 19:50, Ryan P.C. McQuen a écrit : Not necessarily wrong, just the British spelling: http://www.oracle.com/uk/technologies/virtualization/overview/index.html Ah, I didn't know words were spelled differently in British and American English. Thanks for the heads-up. Niki -- Mi

Re: [Slackbuilds-users] virtualbox-kernel: small typo in slack-desc

On Sun, Apr 12, 2015, 10:42 AM Niki Kovacs wrote: Hi, There's a small typo in the virtualbox-kernel slack-desc: virtualisation ==> virtualization Cheers, Not necessarily wrong, just the British spelling: http://www.oracle.com/uk/technologies/virtualization/overview/index.html Niki -- Mic

[Slackbuilds-users] virtualbox-kernel: small typo in slack-desc

Hi, There's a small typo in the virtualbox-kernel slack-desc: virtualisation ==> virtualization Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 1

Re: [Slackbuilds-users] virtualbox-extension-pack

On Tue, 16 Apr 2013 15:22:58 +0400 Nikolay Korotkiy wrote: > Update with attached diff, please. Done in my git branch ; thanks! -RW signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http:/

[Slackbuilds-users] virtualbox-extension-pack

Update with attached diff, please. -- Best regards, Nikolay Korotkiy virtualbox-extension-pack-4.2.10.diff Description: Binary data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slac

Re: [Slackbuilds-users] VirtualBox Question

On 05/24/2012 11:07 AM, Rich Shepard wrote: On Thu, 24 May 2012, King Beowulf wrote: Just set up for multilib (see http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib ) Ed, Did that when I installed the distribution on the new laptop. I'm running Virtualbox just peachy in

Re: [Slackbuilds-users] VirtualBox Question

On Thu, 24 May 2012, King Beowulf wrote: Just set up for multilib (see http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib ) Ed, Did that when I installed the distribution on the new laptop. I'm running Virtualbox just peachy in Slackware64 13.37 multilib. Good to know.

Re: [Slackbuilds-users] VirtualBox Question

On 05/24/2012 10:41 AM, JK Wood wrote: On May 24, 2012 12:18 PM, "Rich Shepard" > wrote: > > The SBo page for VirtualBox notes that it will not build on a stock x86_64 > system. What is meant by 'stock?' What's required to build it on a host > running -13.37

Re: [Slackbuilds-users] VirtualBox Question

On Thu, 24 May 2012, JK Wood wrote: That means it requires the compat32 layer. It still builds as 64 bit, though. A-ha! Thank you, Joshua. My laptop does have the compatibility libraries installed. Now to get acpci to build ... :-( Rich ___

Re: [Slackbuilds-users] VirtualBox Question

On May 24, 2012 12:18 PM, "Rich Shepard" wrote: > > The SBo page for VirtualBox notes that it will not build on a stock x86_64 > system. What is meant by 'stock?' What's required to build it on a host > running -13.37/x86_64? > > Rich > > ___ > SlackBui

[Slackbuilds-users] VirtualBox Question

The SBo page for VirtualBox notes that it will not build on a stock x86_64 system. What is meant by 'stock?' What's required to build it on a host running -13.37/x86_64? Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http:/

Re: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons

On Mon, Sep 12, 2011 at 10:19:56PM +0500, Ozan Türkyılmaz wrote: > 2011/9/12 emmel : > > Still, it built fine and as far as I can tell it ought to work. Except > > my system won't load the kernel module. dmesg says: > > > > [11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy > > s

Re: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons

2011/9/12 emmel : > Still, it built fine and as far as I can tell it ought to work. Except > my system won't load the kernel module. dmesg says: > > [11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy > support in use) > [11788.213363] vboxdrv: Unknown symbol pv_irq_ops (err 0) >

Re: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons

On Sat, Sep 10, 2011 at 02:17:07PM +0500, Ozan Türkyılmaz wrote: > 2011/9/10 Nicolas Kovacs : > > > > I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons > > SlackBuilds. I know they're supposed to be *used* within the GUEST system > > (I've worked with Virtualbox on CentOS

Re: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons

2011/9/10 Nicolas Kovacs : > > I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons > SlackBuilds. I know they're supposed to be *used* within the GUEST system > (I've worked with Virtualbox on CentOS before), but where are they supposed > to be *built*? On the host or guest

[Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons

Hi, I just built and installed Virtualbox on two different desktops, running respectively Slackware 13.37 and multilib-enabled Slackware64 13.37. I duly followed the build instructions, and so far, virtualbox and virtualbox-kernel built OK. I'm a bit confused about the virtualbox-addons and

Re: [Slackbuilds-users] virtualbox-ose.SlacBuild on Multilib install

On Thursday 01 October 2009 08:30:58 Chris Abela wrote: > Hi Heinz, > > Thank you for the instant reply. On my part, I am overwhelmed with other > chores as usual and virtualbox takes long to compile. > > I confirm that gsoap from www.slackbuilds.org plays fine with > virtualbox-ose, but there wa

Re: [Slackbuilds-users] virtualbox-ose.SlacBuild on Multilib install

ng directory `/tmp/SBo/VirtualBox-3.0.4_OSE' kmk: *** [pass_libraries_order] Error 2 ` Chris -Original Message- From: slackbuilds-users-boun...@slackbuilds.org [mailto:slackbuilds-users-boun...@slackbuilds.org] On Behalf Of Heinz Wiesinger Sent: 30 September 2009 14:22 To: SlackBuilds.

Re: [Slackbuilds-users] virtualbox-ose.SlacBuild on Multilib install

On Wednesday 30 September 2009 13:59:08 Chris Abela wrote: > Hi All, > > Not being competent as Alien Bob or Heinz Wiesinger, I must say that I only > managed to install virtualbox-ose-x86_64-1_Sbo.tgz on Slack64 after a heavy > trial and error session. For those who are planning to make such an >

[Slackbuilds-users] virtualbox-ose.SlacBuild on Multilib install

Hi All, Not being competent as Alien Bob or Heinz Wiesinger, I must say that I only managed to install virtualbox-ose-x86_64-1_Sbo.tgz on Slack64 after a heavy trial and error session. For those who are planning to make such an installation the following notes might help. If anyone can explain or

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

Murat D. Kadirov schreef: > On Thu, Sep 03, 2009 at 08:56:02PM +0200, Eric Hameleers (SBo) wrote: >> Murat D. Kadirov schreef: >>> On Thursday 03 September 2009 03:57:36 Heinz Wiesinger wrote: If I understood Eric's multilib setup correctly, running this prior to building virtualbox will

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

Murat D. Kadirov schreef: > On Thursday 03 September 2009 03:57:36 Heinz Wiesinger wrote: >> If I understood Eric's multilib setup correctly, running this prior to >> building virtualbox will result in virtualbox trying to build a 32bit >> binary on a 64bit system, which is not what we (I) want. Vi

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Thursday 03 September 2009 03:57:36 Heinz Wiesinger wrote: > If I understood Eric's multilib setup correctly, running this prior to > building virtualbox will result in virtualbox trying to build a 32bit > binary on a 64bit system, which is not what we (I) want. VirtualBox needs > 32bit- compat

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Wednesday 02 September 2009 09:17:27 markus reichelt wrote: > * Heinz Wiesinger wrote: > > Unfortunately the only way to get vbox on slack64 is by either > > running the binary build (ie virtualbox puel), or by installing > > 32bit-compat libs for the compilation. > > > > Virtualbox needs the g

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

* Heinz Wiesinger wrote: > Unfortunately the only way to get vbox on slack64 is by either > running the binary build (ie virtualbox puel), or by installing > 32bit-compat libs for the compilation. > > Virtualbox needs the gcc, g++ and glibc 32bit components, but only > on build time. It runs fin

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Monday 31 August 2009 08:33:10 Grissiom wrote: > On Mon, Aug 31, 2009 at 05:19, Heinz Wiesinger wrote: > > On Sunday 30 August 2009 19:07:27 Robby Workman wrote: > >> The binary-only is fine - I've been using it on x86_64 since > >> well before any of you knew we had an x86_64 version :-) > > >

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Mon, Aug 31, 2009 at 05:19, Heinz Wiesinger wrote: > On Sunday 30 August 2009 19:07:27 Robby Workman wrote: >> The binary-only is fine - I've been using it on x86_64 since >> well before any of you knew we had an x86_64 version :-) > > I agree. For most people the binary installer might be the b

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Sunday 30 August 2009 19:07:27 Robby Workman wrote: > On Sun, 30 Aug 2009 17:33:49 +0200 > > markus reichelt wrote: > > * Heinz Wiesinger wrote: > > > > So, are there any workarounds/plans to get this hummer talking to > > > > us -64 users? > > > > > > Unfortunately the only way to get vbox on

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Mon, 31 Aug 2009 07:40:40 +1000 Timothy Pollard wrote: > On Sun, 30 Aug 2009 12:07:27 -0500 > Robby Workman wrote: > > On Sun, 30 Aug 2009 17:33:49 +0200 > > markus reichelt wrote: > > > > > * Heinz Wiesinger wrote: > > > > > > > > So, are there any workarounds/plans to get this hummer >

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Sun, 30 Aug 2009 12:07:27 -0500 Robby Workman wrote: > On Sun, 30 Aug 2009 17:33:49 +0200 > markus reichelt wrote: > > > * Heinz Wiesinger wrote: > > > > > > So, are there any workarounds/plans to get this hummer talking to > > > > us -64 users? > > > > > > Unfortunately the only way to ge

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Sun, 30 Aug 2009 17:33:49 +0200 markus reichelt wrote: > * Heinz Wiesinger wrote: > > > > So, are there any workarounds/plans to get this hummer talking to > > > us -64 users? > > > > Unfortunately the only way to get vbox on slack64 is by either > > running the binary build (ie virtualbox

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Sun, Aug 30, 2009 at 05:33:49PM +0200, markus reichelt wrote: > * Heinz Wiesinger wrote: > > > > So, are there any workarounds/plans to get this hummer talking to us > > > -64 users? > > > > Unfortunately the only way to get vbox on slack64 is by either > > running the binary build (ie virtua

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

* Heinz Wiesinger wrote: > > So, are there any workarounds/plans to get this hummer talking to us > > -64 users? > > Unfortunately the only way to get vbox on slack64 is by either > running the binary build (ie virtualbox puel), or by installing > 32bit-compat libs for the compilation. > > Virt

Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

On Sunday 30 August 2009 15:51:40 markus reichelt wrote: > Its buildscript states: > > "NOTE: This will not build on a stock x86_64 system." > > Kind of a bummer for me, sitting on a fresh install of 13-64... > > So, are there any workarounds/plans to get this hummer talking to us > -64 users? Unf

[Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64

Its buildscript states: "NOTE: This will not build on a stock x86_64 system." Kind of a bummer for me, sitting on a fresh install of 13-64... So, are there any workarounds/plans to get this hummer talking to us -64 users? -- left blank, right bald pgpFjqc7cuNE9.pgp Description: PGP signature

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

I believe what he is saying is that you should build a new package so that the old module is removed and the new module is being tracked by the package manager. dae3 wrote: > Il 24/07/2009 alle 13:35, xgiz...@gmail.com ha scritto: > > >> The point of using a SlackBuild is to create a package, b

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

Il 24/07/2009 alle 13:35, xgiz...@gmail.com ha scritto: > The point of using a SlackBuild is to create a package, by recompiling the > kernel module you are corrupting the package and the new module can not be > removed when you uninstall the package. Just my 2 cents. You're not corrupting the

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

I wrote: > I don't think that's a good idea. Why don't you simply point the script > to the new location? > > The VirtualBox GUI is supposed to be able to call the script, so if it > can't find the kernel module, it can make a new one on the spot. This > turns out to be very convenient every tim

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

> The VirtualBox GUI is supposed to be able to call the script, so if it > can't find the kernel module, it can make a new one on the spot. This > turns out to be very convenient every time the user updates or > recompiles the kernel. > > By removing the setup option, you are actually removing us

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

Il 24/07/2009 alle 12:30, Heinz Wiesinger ha scritto: > On Thursday 23 July 2009 12:18:15 dae3 wrote: [...] > > Did you change the sources' install location without modifying all > > references to it? > > Mmm, sort of. > I still think /usr/src is the most appropriate location for kernel module >

Re: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

On Thursday 23 July 2009 12:18:15 dae3 wrote: > Running '/etc/rc.d/rc.vboxdrv setup', one is supposed to be able to > build and install the 'vboxdrv' kernel module on the fly. > > The script however looks for sources in > '/usr/lib/virtualbox/src/vboxdrv/' while the SlackBuild seems to > install th

[Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails

Running '/etc/rc.d/rc.vboxdrv setup', one is supposed to be able to build and install the 'vboxdrv' kernel module on the fly. The script however looks for sources in '/usr/lib/virtualbox/src/vboxdrv/' while the SlackBuild seems to install them into '/usr/src/virtualbox-kernel-2.1.4/vboxdrv'. Did

Re: [Slackbuilds-users] VirtualBox Build Scripts

On Fri, 12 Dec 2008 at 08:10:53 -0600, Robby Workman wrote: > On Fri, 12 Dec 2008 11:33:27 +0100 > Heinz Wiesinger wrote: > > > That rc script is not included in upstream by default. It was written The upstream provides a script called vboxnet, IIRC. But I don't like it, as it's missing special

Re: [Slackbuilds-users] VirtualBox Build Scripts

On Fri, 12 Dec 2008 11:33:27 +0100 Heinz Wiesinger wrote: > That rc script is not included in upstream by default. It was written > by the author of the SlackBuilds on slacky.eu (if I remember > correctly) and at the time I submitted the SlackBuilds for SBo I > didn't really understand them. I se

Re: [Slackbuilds-users] VirtualBox Build Scripts

Darrell Anderson wrote: > I have been struggling to compile VB 2.0.6 in 12.2 with the 2.6.27.7 kernel > configured with the >4GB RAM option. > > Both 1.6.6 and 2.0.6 compile in 12.1 with the 2.6.24.5 kernel and >4GB RAM > option. > > If I disable >4GB option and recompile the kernel, then 1.6.6 and

[Slackbuilds-users] VirtualBox Build Scripts

I have been struggling to compile VB 2.0.6 in 12.2 with the 2.6.27.7 kernel configured with the >4GB RAM option. Both 1.6.6 and 2.0.6 compile in 12.1 with the 2.6.24.5 kernel and >4GB RAM option. If I disable >4GB option and recompile the kernel, then 1.6.6 and 2.0.6 compile in 12.2 with the 2

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

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

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

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 directorie

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 jum

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" = "

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

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 "

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

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 w

[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