LinuxQuestions.org - [SOLVED] Custom kernel breaks Skype on Slackware64 multilib?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Custom kernel breaks Skype on Slackware64 multilib? (https://www.linuxquestions.org/questions/slackware-14/custom-kernel-breaks-skype-on-slackware64-multilib-762570/)

Custom kernel breaks Skype on Slackware64 multilib?

I've got Slackware64 installed on my laptop and made it multilib following AlienBOB's instructions. I've also been working on a custom 2.6.29 kernel, and in the process have seem to have missed something that allows 32 bit binaries to run. Since Skype is really the only 32 bit binary I'm using, that is where I'm seeing the symptoms.

If I try to run Skype from the command line I see this (by the way this happens with both static and dynamic versions of Skype:

Code:

bash: ./skype: cannot execute binary file

Running ldd skype gets me this:

Code:

/usr/bin/ldd: line 161: /lib/ld-linux.so.2: cannot execute binary file not a dynamic executable

Again, the same error happens with both the dynamic and static versions of skype.

What makes me think it is the custom kernel is that on a test Slackware64 machine that uses the stock hugesmp, Skype runs just fine. Well, at least as fine as Skype ever runs on Linux.

So I guess my question is this: Is there a kernel config setting that is needed to run 32 bit binaries on a 64 bit kernel or am I barking up the wrong tree here. I've looked at the config pretty closely and nothing jumps at me, but that doesn't mean much.

I think it is this option:

Code:

  ┌──────────────────────────── IA32 Emulation ─────────────────────────────┐

  │ CONFIG_IA32_EMULATION:                                                  │  

  │                                                                        │  

  │ Include code to run 32-bit programs under a 64-bit kernel. You should  │  

  │ likely turn this on, unless you're 100% sure that you don't have any    │  

  │ 32-bit programs left.                                                  │  

  │                                                                        │  

  │ Symbol: IA32_EMULATION [=y]                                            │  

  │ Prompt: IA32 Emulation                                                  │  

  │  Defined at arch/x86/Kconfig:1949                                      │  

  │  Depends on: X86_64                                                    │  

  │  Location:                                                            │  

  │    -> Executable file formats / Emulations                            │  

  │  Selects: COMPAT_BINFMT_ELF                                            │

Sheesh. Short of putting this in blinking neon lights, I'm not sure how they could have made it more obvious.

Thanks, that solved the problem.