Slackware

StreamThreader · 04-04-2014, 02:33 PM

Hi folks!
Advise configuration for machine, that compile packages for another PCs.
Or point me to documentation for build system.
Or short, recommendation.

Didier Spaier · 04-04-2014, 05:20 PM

I'd simply advise to use a powerful machine with a lot of RAM and preferably the same architecture as the target.

Or on a powerful enough machine you could do compilation in a VM.

kikinovak · 04-05-2014, 05:25 AM

Quote:

Originally Posted by StreamThreader

Hi folks!
Advise configuration for machine, that compile packages for another PCs.
Or point me to documentation for build system.
Or short, recommendation.

I'm using a battered workstation with a Xeon Quad Core processor and lots of RAM, and I build all my stuff in virtual machines using VirtualBox. Before that, I had a spare Dell Optiplex 330 desktop dual-booting 32-bit and 64-bit Slackware, so I could build stuff for both architectures. Advice: don't install any proprietary video drivers on your buildbox.

Alien Bob · 04-05-2014, 07:51 AM

Create a virtual machine using VM software like QEMU or VirtualBox which suppports discardable snapshots.
Every time you compile a package in the virtual machine, you do this in a snapshot image which you throw away afterwards. That way you will start with the exact same Slackware environment every time.

Eric

solarfields · 04-05-2014, 09:27 AM

Just use your most powerful machine and preferably have you Slackware system as "clean" as possible. Best would be virtual machine installation, if your hardware supports virtualisation. I check my SlackBuilds on a Quad core AMD Phenom II machine with 8GB rAM, running Slackware -multilib and have two virtual machines: one of slackware 32bit and another for 64bit.

StreamThreader · 04-05-2014, 11:33 AM

Thanks. about snapshot!
I use this idea

kikinovak · 04-05-2014, 01:00 PM

Quote:

Originally Posted by Alien Bob

Create a virtual machine using VM software like QEMU or VirtualBox which suppports discardable snapshots.
Every time you compile a package in the virtual machine, you do this in a snapshot image which you throw away afterwards. That way you will start with the exact same Slackware environment every time.

When I have to build something that could possibly wreck my system (SlackBuild written from scratch, ...) I often use VirtualBox' "Clone" function. I'm cloning my VM, experiment there, and once everything works OK, I 'git push' my SlackBuilds to the main Git repo and launch them again from the "real" VM (if one can say so).