Running a 32-bit program on Slackware64 - question
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.
Running a 32-bit program on Slackware64 - question
I have the following problem...
There is this small command-line tool I use to convert a certain file format to another. It is free, but not "open" software, so I cannot build it myself.
The previous version was from 2002 and (don't ask me how...) the downloaded binary works fine under Slackware 32 & 64-bits versions.
It uses no libraries, it's just a single executable.
ldd tells me simply that it's "not a dynamic executable".
The newer version, released 6 years later, in 2008, doesn't work any longer on Slackware64, only on the 32-bits version. It gives an error message "No such file or directory" when I try to start it.
My Slackware64 installation is pure 64 bits, no compatibility libraries.
ldd on a 32-bits box says it uses:
- libstdc++.so.5
- libm.so.6
- libc.so.6
- libgcc_s.so.1
I tried to contact the author to convince him to compile a 64-bits version and even offered to help him, but have not received an answer.
I *might* consider installing the multi-lib packages from AlienBOB, but will that help in this case?
It requires tons of switches and a large package of data files to actually do something useful, but it should at least start and give a description of all the options.
IMHO, you need to install the 32-bit compatibility libraries. Because the program need 32bit libstdc++.so.5, libm.so.6 and so on. I have 32bit programs in SW64 facing the same problem but I have no time to install the 32bit compatibility libs. So these are just my guess.
Seems like it works, but as I have no povray files I cannot test it fully, but running l3p gives a load of help options, so I guess it works with 32-bit compatibility installed.
Well, if it gives you the long list of all the options on a multi-lib system, that gives me hope that it will actually work
Now I just have to decide whether to keep my Slackware64 "pure" or install the multilib packages.
I use this box a lot for building (64-bits) packages, so I wanted it to stay as original as possible.
Oh, cruel decisions...
@samac: it actually converts to .pov (from .ldr) but it needs two libraries of files installed.
Last edited by niels.horn; 10-14-2009 at 11:25 AM.
I am in doubt about installing the multilib packages just because I like to keep this machine as "pure" or "original" as possible, so that I can be sure that the packages I create will run on other Slackware64 boxes.
I'll contemplate my decision well...
I might create a new 64-bits VM for creating the packages, with a snapshot of a "clean machine" I can easily fall back to.
The disadvantage is that VMs are a bit slower compiling sources etc...
@MQMan: Hey, thanks for that one!
I installed & ran statifier on the 32-bits box and it created an executable with all the libraries inside.
The resulting file (4x as big ) runs fine on my 64-bits box, without the multi-lib setup.
@brianL: You can sleep without worries: my virgin 64bit box continues "pure"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.