I just stumbled over this via Google Plus:

http://blog.t-rg.ws/20140904/files/file.45/

I do not like the idea of patching the MS binary to spoof a newer version.

Eric

Either that or installing PulseAudio, and it is a real PITA to build 32bit PulseAudio on a 64bit system. And using MS binary on a Linux system is generally a bad idea.

Although I agree that it is a quick and dirty hack and who knows how long it would take for Microsoft to patch that on Skype servers.

fsLeg, FYI, this works fine here (in the 64bit package all the needed multilib dependencies are included).

No, it doesn't. Just tested it, the build script threw the same error:
It looks like there's some problem with variables, because it would be stupid to deliberately trying to install PA sources as the final package. Didn't really look close into the SlackBuild, though.

As for the pre-built package, I prefer to build packages myself.

I suppose I should never have posted "I see no reason to upgrade" since now MS will no longer allow older versions to login. :( So I must give great thanks to the person who posted how to launch Pulseaudio ONLY with Skype. Once I finally feel forced, that I just can't get by with TeamSpeak or other VOIPs, and have to bite the bullet, I will thank and rep him specifically. For now, since I can't recall who that was and am off to work,...

Thank You, Sir.

Thanks, that works really well! :)

I admit I don't like Skype in the first place. But sometimes clients are asking for it. So if a quick & dirty hack will work, I'm happy with it.

ops.. you found a bug on the slackbuild.

Which slackbuild you are run?
you are on slackware 14.1 or current? 32 or 64bit?

use
http://repository.slacky.eu/slackwar.../4.3.0.37/src/
AND
http://repository.slacky.eu/slackwar.../4.3.0.37/src/

however

to build the 64bit version you must:
1) build the 32bit version on a 32bit installation
2) copy the txz on a 64bit in the same directory of 64bit slackbuild
3) launch the 64bit slackbuild

if it fails run it with
bash -x skype.SlackBuild
and post the output

when you build the 64bit version, the slackbuild search the 32bit libraries in the prebuilt 32bit package. If it is not in the same directory of skype slackbuild it try to download it from slacky, but for a bug it use the url of pulseaudio source.

If put the package in slackbuild directory you will solve.

Wow. This is way more hassle than my hack and no less hassle (probably even more) than building 32bit PA on a multilib system. Even docker (which I also successfully tried) would be simplier. You may argue that all of this is done in a single script. Well, there's this package called sbotools which handles building of 32bit packages on a miltilib system pretty good, so the "right" way is just as automated.

I tried SlackBuild from slackware64-14.1 directory on a Slackware64-14.1 multilib. Didn't try it with a 32bit environment exported.

I don't have a multilib system, so I've no other way.

Who have a multilib system does not require an all-in-one package.
In these thread there are other skype slackbuilds built over a multilib system that work better than an all-in-one package.

But who have not (and don't want) a multilib system, need the all-in-one packages built on two different slackware installation.

Some people do not want to build every package from source (this is Slackware, not Gentoo) and are happy with using pre-built packages from trusted sources or packagers.

Zerouno's package can be installed by non-skilled people even, and with that one package you have a working Skype on an otherwise 64-bit pure system, and a pulseaudio that only runs when Skype is running. That is a nice prospect for a lot of people.

So, thank you zerouno.

Eric

zerouno, you are great!

Warning: Minor Rant

Thank you for this bit of information, even if only to realize that Microsoft is still at it as devious, control freaks. They've been doing this a long time. Back in the day, besides "offering" to delete any OS/2 partition during Windows install, they relabeled the extended partition descriptor from 05h to 0fh and literally the only difference was exactly one bit, the descriptor itself. Then they used the exact same descriptor for an NTFS partition as an HPFS partition so that OS/2 would see them as corrupt HPFS partitions. The list is long and now this. Who does it serve to force an upgrade in a Linux version that is essentially in name only other than the exclusion of ALSA-only systems? That older versions will run, and apparently work just fine if the "descriptor" is spoofed reaffirms that as much as Microsoft would like to be seen as more community oriented than in the past (now that they've destroyed so many competitors with both legitimate and illegitimate methods and gained 90+% market share) they are still the same old sharks. Dirty deeds, done dirt cheap. Disgusting!

zerouno's package worked flawlessly