Who are you to tell anyone what they must or must not do?

Adam

Is more easy to install an entire ghost operating system, than a custom kernel? Interesting ...

GoogleEarth 6.0 is happy on the 64 bits platforms. Just do an update/upgrade.

As I said, that's my opinion on that subject. Your opinion may be very different, right?

That line about "must stay in Pure64" was a separate paragraph about your stated, silly opinion on marrying Sudanese or Swedish girls, so it no longer looked like an opinion, but rather an order.

Adam

Both Sudanese or Swedish girls are beautiful female Homo Sapiens Sapiens, like your species, and they can give you beautiful children. The rest is matter of taste.

Anyway, I said my opinion in that subject. Fell free to earn something from that thing or ignore it. Cheers!

Yeah, just run 2 commands:
upgradepkg --reinstall --install-new *.t?z
installpkg *?/*.t?z
and it's done.

Thanks Eric. I saw this post earlier but wasn't quite sure on the special treatment for gtk+2, gdk-pixbuf2 and pango. I had a guess, after looking at the script, but waiting in the hopes you would clear the air. I was not disappointed.

FWIW I like the way you put multilib together makes perfect sense to me.

Eric,

I don't know WHEN I'll get to rebooting the necessary machine ... too busy at the moment. As I said earlier, I suspect the problem lies with my incomplete installation of your compat32 libraries. I'll just wait until the new release of SW64 occurs and update your 32 bit libraries at that time.

I don't want to derail the thread, but yes -- GoogleEarth 6.0 is happy on 64-bit platforms. 64-bit MULTILIB platforms. Dolt. There isn't one single 64-bit executable in either the .deb or the .rpm 64-bit Google Earth 6.0 package. If you're going to patronize others for expanding their opportunities at least know what you're talking about. There are very legitimate reasons for wanting to use a multilib 64-bit Slackware.

I like being multi-lib; It gives the flexibility I need on some parts. For example running proprietary 32-bit software with Wine. I have no likes for remaining fully 32bits just because not all my programs are able to run 64 bits. I love being able to run whatever is capable of running 64bits as that, and be able to run those programs that are not capable.

Rewriting a proprietary program of which I do not have the source code and is several gigabytes in size is NOT something I am going to dive into just because my system is 64 bits and I want that particular program be able to run 64 bits. I rather recomple existing source that enables me to do what I want to do.

The comparison between the swedish and nigerian girl is completely twisted. We're talking about compatablilty here. A better comparison would've been electrical plugs and voltage. You have machine X that runs on 230V with an english style plug, but alas, you live in the Netherlands... netherlands does not have english plugs. So, would you move to england to use that particular machine, or would you rather buy a converter that would allow you to plug the machine in at your own house in the Netherlands where they don't have english plugs? (I may have used the wrong terms, but I hope you get the idea of what I mean)

I think there is wisdom in the Slackware approach: a 64-bit and a 32-bit distro, both completely true to their 32 and 64 bit nature, with indeed the ability to have a plug in the form of rebuilt libraries (not kernel!) on the 64 system that will allow you to run your 32-bit programs.