[SOLVED] Slackware 13 64 - Alien Bob's multilib and Wine
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
As to the OP's exact problem, hard to tell. Missing some 32bit compatible packages? Wrong versions of 32bit compatible packages?
The whole multilib thing is new to me. I have a full standard Slackware setup, and I loop mounted the 32-bit Slackware for the 32-bit package tree. I downloaded Alien Bob's 13.0 multilib packages. I ran the multilib instructions as root. I tried to run winecfg and wine as normal user. I'm no expert by any means but I have been compiling software and and running slackbuilds since the first day I moved to Slackware last August, without a single problem. I even learned to modify Slackbuilds so that I could install newer source. No problems at all until now! But still it remains very exciting learning all about this anyway, so I never mind coming up against problems!
wine gives the "Cannot execute binary file" for many reasons.
Most common are:
wine not setup after install (winecfg)
File permissions were not changed to executable
File is not in a format that wine recognizes as executable
File is on a drive that does not allow execution of files
With more info, we may be able to get to the bottom of this issue.
Hi, and thank you for your help. I now see that *any* 32-bit program I install reports the same error - "Cannot execute binary file" - so this isn't a Wine issue. It seems that the multilib process hasn't worked out for me, but I'm completely unsure why that might be so, given that I followed every step religiously, and my system is pretty much a stock Slackware, full install. The only significant system change I made was to upgrade the kernel to 2.6.33.
The question now is, how do I restore the system and start again, or troubleshoot to find the problem? The multilib process didn't report any errors, except for those expected errors Alien Bob mentions.
I know I haven't given much information to you to be of help here, so don't trouble yourself over it, but a pointer to how I might output the various steps of the multilib process to a log file would help, if anybody could advise.