Do you require 32bit compatibility in Slackware64-current?
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.
View Poll Results: Do you require 32bit compatibility in Slackware64-current?
It would be nice if all programs played well with 64bits, however some just don't. If you have one or two of these programs that you have to use, and you do not wish to have to run two different systems, then you should probably answer yes.
If not then no would be a good choice.
Nobody is forcing the developers of our favourite system to do anything that they don't want to, I am sure that they look in from time to time and can make educated guesses as to what the system and it's users needs.
Please try to keep speculation and personal politics to a minimum, after all it is just a yes/no question
32-bit compatibility would make migration easier. However, I think I can swing it with with a separate 32-bit root, as opposed to a multilib setup in a common root. So I'd just need to have 32-bit compatibility turned on in the kernel (I build my own anyway). I'd just do a full install of 32-bit slackware in one directory tree, and 64-bit slackware in another directory tree, and pick which one to be root at boot time. This could be done via initramfs, initrd, or a patch I wrote for the kernel to allow choosing a subdirectory to be root on the parameter line.
By the looks of today's changelog, multilib will at least be possible in Slackware64. I don't expect the Slackware team to have to maintain the extra packages required for multilib, however I think it's nice that it will at least be possible.
By the looks of today's changelog, multilib will at least be possible in Slackware64. I don't expect the Slackware team to have to maintain the extra packages required for multilib, however I think it's nice that it will at least be possible.
Would be nice if one could just install (some) Slackware32 libraries into a Slackware64 system and end up with a multilib system (maybe with an optional multilib support package to set up for it). But I haven't used multilib, yet, so I don't know exactly what that requires.
I'd appreciate a multilib system but can live without, especially if going multilib makes everything (maintainance for the Slack team, compiling) much more complicated and if it brings weird behaviour.
Mon May 25 17:52:56 CDT 2009
d/binutils-2.18.50.0.9-x86_64-2.txz: Changes to enable multilib support.
Thanks to Fred Emmott.
d/gcc-4.3.3-x86_64-4.txz: Changes in specs file to enable multilib support.
Thanks to Fred Emmott.
So it appears Fred is helping them out, and Slackware64 will have 32-bit support.
Maybe we can install 32-bit packages with some care, and they'll run, but perhaps
not be *officially supported* by Slackware.
Last edited by Bruce Hill; 05-26-2009 at 06:26 PM.
Re: Building wine on Slackware64
You may need a few extra items. Run over to http://www.slamd64.com/download and in particular check out the slamd64/slackware64-current directory. There are a number of packages for the a, d, l, n, x series. From the readme:
Quote:
This directory contains the start of 32-bit compatibility packages for
Slackware64-current.
Tested with:
- Skype (dynamic build)
- RTCW: ET
- Wine (built withs script from builds.slamd64.com)
Slamd64's c/ set isn't quite right for this purpose; my goal with these
packages is to add 32-bit compatibility as unobtrusively as possible.
...
Enjoy.
Primo: easier and quicker distro-upgrade from previous version of Slack.
Secundo: there are to many software not ready for 64-bit (ie. Wine, Skype, Sane)...
Transitions in the computer world are a pain in the butt. I personally dislike setting up a new operating system, personalizing my settings, personalizing my wife's settings, etc. One of the things that I really like about Slackware is that, after I set it up, it basically runs unattended without problems -- except for applying the occasional security patch.
The important things for me are the applications. I need stuff to work and to work well. Slackware is an excellent distribution for adding lots of esoteric libraries to get even more esoteric programs to run (e.g. QGIS, GRASS, Wine, Scribus, Inkscape). If 32-bit compatibility is necessary for some of those programs, then I'm all for it.
I'm not saying that the full Slackware installation needs to have everything pre-installed, but I'd like to be able to use 32-bit libraries if I need them.
However, this may be a moot point. The above-quoted section from the --current changelog shows that 32-bit compatibility will be enabled.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.