LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   skype on slackware64-current (http://www.linuxquestions.org/questions/slackware-14/skype-on-slackware64-current-743613/)

alexiy 07-29-2009 04:06 AM

skype on slackware64-current
 
Hi,

Could someone who succeeded in running Skype 2 on slackware64-current give me some advises how to run it...

Unfortunately I'm unable to do that. When I type "./skype" in CLI it says me: file not found when the file is in a folder it was installed and has run permissions...

Thank you in advance.

ppr:kut 07-29-2009 04:15 AM

skype currently has no 64bit client available (it's in development though), so you'll need quite an amount of 32bit compat libs installed to be able to run skype on Slackware64.

rvdboom 07-29-2009 04:15 AM

You need to recompile the kernel (or load the appropriate module, if it is compiled in the default Slack kernel, I don't know) to support 32bits executables.
Then you'll need the 32bits compat libs from Fred Emmott, as Skype need them.
It should work well afterwards. It surely does here.

alexiy 07-29-2009 04:58 AM

Yes I know it needs some 32 libraries... The question is which ones. On my current opensuse x86_64 (now I do want to try slackware) skype always was mentioned which library it needs when I was running it. So it was no so difficult to find a proper one. But here there is only error message: "file not found..." so what exactly it needs - not clear...

Alien Bob 07-29-2009 05:53 AM

Quote:

Originally Posted by rvdboom (Post 3623976)
You need to recompile the kernel (or load the appropriate module, if it is compiled in the default Slack kernel, I don't know) to support 32bits executables

There is no need to recompile the slackware64 kernel. It already supports 32bit binaries.

Eric

zhjim 07-29-2009 06:15 AM

Quote:

Originally Posted by alexiy
But here there is only error message: "file not found..." so what exactly it needs - not clear...

You for sure are in the right directory? The reason why I'm asking is cause the error message does not make any sense then...
Anyways just for clearification the "./" part tells the cli to use the current working dir. So make extra sure with whereis skype. cd to the dir whereis found skype. (all on cli and taken that the binary is called skype)


Quote:

Originally Posted by alexiy
Yes I know it needs some 32 libraries... The question is which ones. On my current opensuse x86_64 (now I do want to try slackware) skype always was mentioned which library it needs when I was running it. So it was no so difficult to find a proper one.

I never used skype on linux but does it realy print out the libraries? Or do you mean when you install skype that it prints out the dependencies?
None the less use the ldd command to find out which shared libraries a programm needs.

Code:

ldd skype
You need to be in the directory where the binary you want to check on resides. Else give absolute path.


P.S.
congrats on trying out Slackware. IMHO its far better for learing linux than SuSe will ever be.
I went this way my self and am more than happy

alexiy 07-29-2009 07:17 AM

Quote:

Originally Posted by zhjim (Post 3624099)
You for sure are in the right directory? The reason why I'm asking is cause the error message does not make any sense then...
Anyways just for clearification the "./" part tells the cli to use the current working dir. So make extra sure with whereis skype. cd to the dir whereis found skype. (all on cli and taken that the binary is called skype)

Yes, I've double checked this... everything is in /usr/share/skype and a SH script is in /usr/bin. That way it was installed from slucky.eu...

ldd ./skype gives:
not a dynamic executable

Quote:

Originally Posted by zhjim (Post 3624099)
P.S.
congrats on trying out Slackware. IMHO its far better for learing linux than SuSe will ever be.
I went this way my self and am more than happy

Hopefully I will manage it... I tried already mandriva, ubuntu, fedora... but gave up with them for some reasons...

TwinReverb 07-29-2009 07:48 AM

In terms of Skype on Slackware64 using the Slamd64 32-bit compatibility libraries, your mileage may vary. It may work for you, but it did not for me, even when I was using Slamd64. (For those of you who want to respond to this, don't bother: no one on #slamd64 on FreeNode could figure out why, and I'm sure not going to try it again. And no, this is not a slam (pardon the pun) on Slamd64 or Slackware64.)

I just dual boot: Slackware-Current and Slackware64-Current. When I get home to my wife from South Korea, I may not have a need for Skype any longer.

For what it's worth, 64 bit is lagging on both Windows and Linux, so it's not like this is Slackware64's fault or Skype's fault. They have a beta test for Windows 64 bit, and they say they are working on one for Linux. I have yet to ask anyone how the beta version is working on Windows.

My advice: either dual boot or be patient.

alexiy 07-29-2009 10:02 AM

Any way I believe it should work under slackware64... it works in others 64bit distros, why slackware should be an exception...

Anyone?

sxtytwofrd 07-29-2009 12:22 PM

Hello,

I have installed Skype on Slackware64 current. I downloaded the 32bit compatibility packages from the Slamd64 current. These are located under the "c" package directory. Here is a link:

http://mirrors-sanfrancisco.hostgis....ent/slamd64/c/

I installed Skype using the Slackbuilds.org script. Then I installed the four following packages from the Slamd64 compatibility packages:

aaa_elflibs32-12.2.0-x86_64_slamd64-1.tgz
alsa-lib32-1.0.17a-x86_64_slamd64-1.tgz
gcc-compat32-4.3.3-x86_64_slamd64-3.txz
xlibs32-7.3-x86_64_slamd64-6.tgz

And that was it. Skype should work for you. I have been using Skype for about a month or so like this and have had no problems. Hope this helps.

Rob

JazzItSelf 07-29-2009 02:29 PM

I'm sure the answer to this is yes, but just to be thorough, you still need the 32-bit compatibility libraries even if you're going to use the statically linked version of skype, right?

--Chad

metrofox 07-29-2009 03:21 PM

Well, I've a question to ask you, if I download a software to compile, it's all written in 32 bit, does the normal compilation work? (I mean, ./configure; make; make install(I always make a slackbuild but you know what I mean...)) Or do I need of a cross compiler? :)

Alien Bob 07-29-2009 04:20 PM

Source code is not "written in 32 bit". It is architecture-independent by nature.
If you compile the source on Slackware64 you will get 64bit binaries. If you compile the same sources on 32bit Slackware you will get 32bit binaries.

In order to create 32bit binaries on Slackware64 you will need the multilib compiler and glibc installed that Fred Emmott packaged for Slackware64, in addition to all the "compat32-" packages containing commonly used libraries.

Eric

alexiy 07-30-2009 04:20 AM

Hi sxtytwofrd, thanks mate for the help. It works perfectly.

Just to finish this story (might be useful for someone else): to force working my Logitech Quickcam Messenger I took v4l1 libs from slackware12.2, preloaded it before starting skype and now skype and video work.

P.S. Why do we use the 32bit emulation libraries from slamd64? Does it mean that slackware64-current doesn't have its own so far?

Alien Bob 07-30-2009 06:52 AM

Quote:

Originally Posted by alexiy (Post 3625227)
Why do we used the 32bit emulation libraries from slamd64? Does it mean that slackware64-current doesn't have its own so far?

Those 32bit compatibility libraries created by Fred Emmott are hosted on the slamd64 repository (ftp://anorien.warwick.ac.uk/slamd64/...are64-current/) but they are really for Slackware64, the packages have been compiled on a real Slackware64 too.

There will not be 32bit compatibility packages in Slackware64 when it ships. Those will have to be obtained from another source: from Fred Emmott or through me (I will make a set of multilib packages and scripts available for download from my repository after Slackware 13.0 ships).

Eric


All times are GMT -5. The time now is 10:40 PM.