You are not logged in.
Pages: 1
is there anyway to get skype working in 64 bit arch, i am totaly lost..
( sorry if this has been asked before, i couldent find anything )
Last edited by xhhux (2008-08-20 01:25:05)
Offline
use 32-bit emulation? That's the only solution I could think of. Skype hasn't talked much about getting their product to work in 64-bit environments. No other program can access their protocol because it's closed. So that's probably the best you can do.
Offline
use 32-bit emulation? That's the only solution I could think of. Skype hasn't talked much about getting their product to work in 64-bit environments. No other program can access their protocol because it's closed. So that's probably the best you can do.
ok, how does one go about doing 32bit emulation?
Offline
Berticus wrote:use 32-bit emulation? That's the only solution I could think of. Skype hasn't talked much about getting their product to work in 64-bit environments. No other program can access their protocol because it's closed. So that's probably the best you can do.
ok, how does one go about doing 32bit emulation?
This isn't "emulation", but I suspect that's what the post above is referring to:
http://wiki.archlinux.org/index.php/Arc … bit_system
The approach described on the page linked just above lets you run 32-bit apps in an isolated 32-bit Arch subsystem.
The other option is to install the necessary 32-bit libraries. I think this wiki page discusses this, and it lists Skype as one 32-bit app that's been tested with this approach.
Offline
is there anyway to get skype working in 64 bit arch, i am totaly lost..
( sorry if this has been asked before, i couldent find anything )
just install the package from AUR.
if you have yaourt, you can just do
yaourt -S bin32-skype
Offline
just install the package from AUR.
if you have yaourt, you can just do
yaourt -S bin32-skype
@ rooloo: So is it safe to install any bin32-packagename in an Arch64 system? The appropriate 32-bit libraries are pulled in and installed in locations where they won't conflict with the 64-bit libs? I've been using the chroot Arch32 method to avoid the possibility of any such conflict, but maybe that's being overly paranoid.
Last edited by dhave (2008-08-20 00:46:08)
Offline
@ rooloo: So is it safe to install any bin32-packagename in an Arch64 system? The appropriate 32-bit libraries are pulled in and installed in locations where they won't conflict with the 64-bit libs? I've been using the chroot Arch32 method to avoid the possibility of any such conflict, but maybe that's being overly paranoid.
I would think that they would get installed under lib32XXX, wouldn't it?
That would make sense and would not have name collisions with the 64 bit libs under lib64XXX. I think the best way is to find out.
Unfortunately I do not have a 64 bit machine. But maybe someone with a 64 bit install can try installing a couple of 32 bit apps and see if they work.
Last edited by Inxsible (2008-08-20 01:22:00)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
rooloo wrote:just install the package from AUR.
if you have yaourt, you can just do
yaourt -S bin32-skype
@ rooloo: So is it safe to install any bin32-packagename in an Arch64 system? The appropriate 32-bit libraries are pulled in and installed in locations where they won't conflict with the 64-bit libs? I've been using the chroot Arch32 method to avoid the possibility of any such conflict, but maybe that's being overly paranoid.
apperantly not I just installed and everything works perfectly, thanks rooloo
Last edited by xhhux (2008-08-20 01:24:05)
Offline
all my 32 bit libs are in /opt/lib32/, but yeah, that's the point dhave.
just check the AUR for a package build that starts with lib32 (there is shitloads). Open it and view it, the few bash commands inside the build{} should explain everything.
edit: only issue with using 32 bit libs, you have 2 libs of the same thing per package. 64/32 bit respectively. On small machines with limited space this is a potential problem. But, for the most part, all old and small hardware is gonna be running i686 anyway. so it's a moot point.
Last edited by rooloo (2008-08-20 01:26:50)
Offline
all my 32 bit libs are in /opt/lib32/, but yeah, that's the point dhave.
just check the AUR for a package build that starts with lib32 (there is shitloads). Open it and view it, the few bash commands inside the build{} should explain everything.
edit: only issue with using 32 bit libs, you have 2 libs of the same thing per package. 64/32 bit respectively. On small machines with limited space this is a potential problem. But, for the most part, all old and small hardware is gonna be running i686 anyway. so it's a moot point.
O.K., thanks, rooloo. You've clarified something that's been foggy to me since I first went over to Arch64 (all of about two months ago!).
Offline
Pages: 1