LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 13 64 - Alien Bob's multilib and Wine (https://www.linuxquestions.org/questions/slackware-14/slackware-13-64-alien-bobs-multilib-and-wine-807636/)

Gerard Lally 05-14-2010 12:52 AM

Quote:

Originally Posted by cwwilson721 (Post 3967555)
wine (32-bit compiled on a 64 bit SW13 system), worked perfectly fine on my Slackware Multi-lib system.

Installed the multi-lib according to alienBoB's instructions, and then compiled wine from source.

Did you use the slackbuild script when compiling from source or just the usual ./configure && make && sudo make install?

Quote:

Sounds like the OP doesn't know how to setup wine. (I'm guessing he never ran
Code:

winecfg
after compiling/installing
Yes I think it's more to do with my lack of knowledge. I did run winecfg though, but only after trying first to run wine (sheepish grin).

:)

Gerard Lally 05-14-2010 01:10 AM

Quote:

Originally Posted by disturbed1 (Post 3967573)
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!
:)

Gerard Lally 05-14-2010 04:24 AM

Quote:

Originally Posted by cwwilson721 (Post 3967582)
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.

cwwilson721 05-14-2010 05:37 AM

Easiest way to setup multilib is to download all the 32 bit compat pkgs that AB has on his site, get the wine source code, get the proprietary drivers for your video card, then:
  • Install the video drivers
  • Install the compat pkgs (I do them all twice, because some pkgs rely on packages that will install later. No harm to the system to install twice)
  • Compile and install wine
  • Run winecfg
  • Done

Alien Bob 05-14-2010 06:43 AM

Quote:

Originally Posted by gezley (Post 3968089)
The only significant system change I made was to upgrade the kernel to 2.6.33.

Perhaps you forgot to enable 32bit binary support in your 64bit kernel?

Eric

Gerard Lally 05-14-2010 11:04 AM

Quote:

Originally Posted by Alien Bob (Post 3968233)
Perhaps you forgot to enable 32bit binary support in your 64bit kernel?

Eric

Eric you are a genius! Thank you! I'd never have guessed! Working perfectly now.

Thanks to everybody else who helped as well.


All times are GMT -5. The time now is 08:32 PM.