Re: [Slackbuilds-users] qt5 build fail

> build completed successfully on my vm with 8gb RAM allocated, (and 12G+ > free disk space) > so swap+ram should be>7GB to complete. - may be more with docs. I managed to build it on my low spec VM with just 2 GB of RAM with 8GB SWAP :) it just takes longer -- Willy Sudiarto Raharjo

Re: [Slackbuilds-users] hope this isn't a stupid question

Thank you everyone for the responses! "Doctor, I have come to ask you to tell me everything you know about the night." -

Re: [Slackbuilds-users] hope this isn't a stupid question

Glenn this setup is very effective.  I use it too -- I run current and I keep a partition with a stock 14.2 VM and -current VM (both Virtualbox).  When it's time to test, I clone the VM, do my testing, then destroy it. I keep the 'master' VMs up to date but stock in all other respects so the

Re: [Slackbuilds-users] Qt5 ... newer versions available

On 2020-04-08 17:26, Tim Dickson put forth the proposition: > will there be a new version of qt5-webkit in line with the new qt5 ? I'll be looking at that soon. There has just been an update of Qt LTS to 5.12.8 today, so I'm currently doing a test build of that. -- Dave The antibloat squad!

Re: [Slackbuilds-users] Qt5 ... newer versions available

will there be a new version of qt5-webkit in line with the new qt5 ? thanks, Tim --- This email has been checked for viruses by AVG. https://www.avg.com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] qt5 build fail

build completed successfully on my vm with 8gb RAM allocated, (and 12G+ free disk space) so swap+ram should be>7GB to complete. - may be more with docs. thanks all. Tim --- This email has been checked for viruses by AVG. https://www.avg.com ___

Re: [Slackbuilds-users] hope this isn't a stupid question

i use qemu 4.0 to do just that (4.1 requires stuff from current, and I didn't want to pollute my host slack stable) something like qemu-img create -f qcow2 /data/images/slack14.2_64bit_base.qcow2 100G will create a virtual disk drive 100G which you can snapshot, if you want to reverse changes,

Re: [Slackbuilds-users] hope this isn't a stupid question

On 2020-04-08 10:44, Glenn Becker put forth the proposition: > Hi - > > My understanding was that SlackBuilds were 'guaranteed' to run on -stable > rather than -current. Maybe that's wrong, or has changed? You are correct. That hasn't changed. > G >

Re: [Slackbuilds-users] hope this isn't a stupid question

Hi - My understanding was that SlackBuilds were 'guaranteed' to run on -stable rather than -current. Maybe that's wrong, or has changed? G "Doctor, I have come to ask you to

Re: [Slackbuilds-users] hope this isn't a stupid question

On 2020-04-08 15:30, Slackbuilds Users put forth the proposition: > Hi Glenn > > If you're going to use slack-current as your main system why would you want > to have slack-stable running in a VM? I would have thought you would have > wanted to develop your SlackBuilds in a VM  machine running

Re: [Slackbuilds-users] hope this isn't a stupid question

Hi Glenn If you're going to use slack-current as your main system why would you want to have slack-stable running in a VM? I would have thought you would have wanted to develop your SlackBuilds in a VM  machine running slack-current. Alex On 08/04/2020 14:43, Glenn Becker wrote: Hi - I

Re: [Slackbuilds-users] hope this isn't a stupid question

On Wed, Apr 08, 2020 at 09:43:27AM -0400, Glenn Becker wrote: And I was wondering ... if I ran slack-current as my main system, but ran slack-stable in a VM, could I use the latter to work on my SlackBuilds? Yes. The VM is essentially a second, independnent, machine. I do this myself when

Re: [Slackbuilds-users] hope this isn't a stupid question

On 2020-04-08 09:43, Glenn Becker put forth the proposition: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > usually done double-, triple- and occasionally more- boot machines, but my > distro-hopping is (I think!) coming to an end. > > And I was wondering

Re: [Slackbuilds-users] hope this isn't a stupid question

Simple answer is yes. Treat the VM as if it were another machine. That said it's possible to do the slackbuild dev/testing on slackware-current, but it takes quite a bit more effort (and library duplication, which you'd be doing in the VM anyways) I'm sure someone else can offer more

[Slackbuilds-users] hope this isn't a stupid question

Hi - I am thinking of buying a smallish laptop to dedicate to Slackware. I've usually done double-, triple- and occasionally more- boot machines, but my distro-hopping is (I think!) coming to an end. And I was wondering ... if I ran slack-current as my main system, but ran slack-stable in a VM,

Re: [Slackbuilds-users] qt5 build issue

On 2020-04-08 11:27, Slackbuilds Users put forth the proposition: > looking closer, it looks like I'm out of virtual memory. I don't have a swap > partition on my build vm, but it has allocated 6GB ram, but that  seems > insufficient for this version of qt5. I'm re-running it with 8GB ram, and >

[Slackbuilds-users] qt5 build issue

extra log info from /var/log/sbopkg/sbopkg-build-log|tail -n50 [258/2543] /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING