Build packages for Slackware and Slackware64 on a single box?
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.
Build packages for Slackware and Slackware64 on a single box?
Hi,
I just bought a brandnew (well, only three years old ) PC that I intend to be a build box for some custom Slackware packages. Since I intend to use Slackware as well as Slackware64, depending on the hardware, I want to build all packages for both architectures.
Short question: is it possible to build packages for both architectures on Slackware64? Or do I have to setup something like a Slackware/Slackware64 double boot and then build 32bit-packages on the 32bit-system, and 64bit-packages on the 64-bit system? So far, the only 64bit-machines I'm using are servers (running CentOS 64bit), and all my desktop experience is 32-bit.
Each has its pros and cons, choose what's appropriate to you.
For the first two it's a good idea to use btrfs to make a clone of clean Slackware install, build packages using it, and then delete it. Virtual machines often have snapshots or some similar feature for this.
There's also multilib. But for myself, I prefer the chroot method. It's simple, not secure (running a build of your own code shouldn't need security), and doesn't require any special handling after setting up. If someone needs more security, do LXC. Even more than that, use a VM. Still more, get an unconnected box.
My machine is actually a multi-boot (36 way, to be exact). I can boot into the 64-bit system, or the 32-bit system, or even the 32-bit system with a 64-bit kernel. I'm also going to add a multilib one in there, but haven't, yet. I'm putting older versions and other distros in there for expanded testing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.