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.
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...
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.
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.
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...
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.
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
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
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...
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.
Last edited by TwinReverb; 07-29-2009 at 07:51 AM.
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:
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?
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?
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.
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?
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).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.