Hello again!

A quick question. I am trying to decide whether or not to install Slackware_64, and I am curious about something.

Will I be able to build / install and run all of my favourite Slackbuilds 32-bit apps. on Slackware_64? I am already running Slackware 13.37 on four machines (all 32-bit versions), and I have not yet installed the 64-bit version (I am hoping to do so on a new system I am purchasing soon...).

This has me worried, because I have read that having BOTH the 32-bit AND 64-bit versions of some libraries, etc. can cause problems? Am I mistaken?

I was reminded to ask about this when I read Cultist's reply to another one of my posts...

Just curious...

Andre. (Z_Tagr)

AFAIK, most apps should compile fine if you set up a multilib system. Follow AlienBob's multilib tutorial:
http://alien.slackbook.org/dokuwiki/...kware:multilib

I wouldn't bother with 64bit + multilib. If you have 32bit apps to run, then run a 32bit OS and save yourself some trouble. Running multilib introduces a requirement for additional administration/maintenance to your system. IMO 64bit is not worth it unless you have no need for 32bit apps and can run a pure 64bit system.

3 members found this post helpful.

Nearly all slackbuilds will compile perfectly fine on a 64-bit system. The only ones that won't are the ones that come only in precompiled 32bit-only binary such as Google Earth, which will require alienbob's multilib packages (linked by Sycamorex above). Wine is a major exception to this I should point out - if you plan on running wine, it must be compiled as a 32 bit system with multilib installed for it to run on a 64 bit system.
Of all the slackbuilds I've ever installed, I've only run into 3 that actually require multilib - Google Earth, Wine, and zSNES.

The part of your post about problems with having two versions of the same library is correct, but the multilib install will allow them to be installed concurrently without issue. And to expand on what I've already said, since most slackbuilds will compile and install without issue on a pure 64-bit slackware, you won't even need the 32-bit libraries until you find something that runs only in 32-bit.

1 members found this post helpful.

Thanks again Cultist!

That was EXACTLY what I wanted to know!

I have just today purchased a new triple-core 64-bit system, and I am planning on installing Slackware-64 on that machine...; well, actually, THIS MACHINE! I'm taking it for a "test-run" right now!

Cheers!

Andre. (Z_Tagr)

I would also like to say thanks to Gazl for his suggestion, and thanks to sycamorex for the link to the tutorial! That will come in handy!

later...
Andre. (Z_Tagr)

Yep, you were "dead-on", Cultist!

I installed Slackware64 on my brand-new triple-core notebook, and have already installed one of my favourite packages (rosegarden), and all of its deps. No problem!

I am right now getting ready to "multilib" it, so that in the event that I DO need a 32-bit-only app., I'll be ready. Hech, "multilib" is just a smart thing to do, regardless! You never know, and I may as well do it now, while the system is still "fresh", so to speak...

The "alienbob" article is well written, and easy to follow, so I shouldn't have any problem with this...

Thanks again!

Andre. (Z_Tagr)

Oh, and I forgot to mention...

What I asked about wasn't strictly what I meant! I did not realize that MOST SlackBuilds apps. and libs are 32-and-64 bit! I did NOT mean to imply that I wanted to install 32-bit-only apps! Actually, the ones that were referred to (pure 32-bit, I mean) are really not of any concern to me (at least, not for the foreseeable future, anyways!).

Just to clear that up!

Cheers!