Slackware64 and 32-bit compatibility
 

Sorry but I have no idea where to start with this.

If I want to be able to run and compile 32 bit applications I need to get the proper lib32 stuff...

How do I go about doing this? Can someone point me in the right direction?

I mostly need openoffice...

That's not a valid option, at least not at this point (which does not imply that it will *ever* be).

Using this tarball:
http://ftp-atl.osuosl.org/pub/openof...l_en-US.tar.gz
you should be able to adapt my SlackBuild script at SlackBuilds.org to build a package for x86_64. I'm not where I can download it at the moment, but I'll try to get that taken care of in the next few days and put something online.

I'm actually wondering along the lines of a 32 bit chroot environment. There arn't many things that I would like to run for 32 bit and wonder if this would be a better solution. Unless I'm grossly underestimating the dependencies of running graphical applications this way... if it's even possible.

I just built the 64 bit version of open office and it works perfect. Seems a little faster than the 32 bit.
I used the Slamd64 build.

http://builds.slamd64.com/Office/openoffice.org/

just run this and you get all the Slamd64 builds if you like.

git clone http://builds.slamd64.com/slamd64builds.git

Ah yes, I somehow forgot about the slamd64 builds - that is indeed a good choice.

I've been running 64bit OpenOffice for quite a while while testing Slackware64(tm) I just modified the 32bit SlackBuild from Robby.

Among other things that I tested were postgres, qcad and php with mcrypt.

For programs that do need 32bit libs, wouldn't installing packages from Slackware 32's 'l' series work?

I believe multilib 'may' require a few different setups with gcc when installing... I've never fully followed Linux from Scrach let alone the multilib cross compile http://cross-lfs.org/view/1.1.0/ But you would at the very least need duplicate copies of the c library compiled for 32 bit and 64 bit.

To install 32 bit packages, you would need all of their dependencies to be 32 bit without messing up your 64 bit packages that may already be installed to meet dependencies for your 64 bit applications.

Currently no.

This is an issue also to me because i play Enemy Territory:Quake Wars and it's 32bit....so, what's best option to run it in SLK64 ?

TIA,
AJSB

So, in the other thread it became apparent that currently slackware64-current is "multilib-capable', and no 32-bit compatibility libs are available at this time ... but maybe later ? You may need to just wait a while and check up on it to see what was changed or added or fixed.

Hmm,
Right now I'm watching TV with TVtime that I built several months ago for Slack 12.2 from a SlackBuild.
I'm definitely not qualified to get in to a debate on this but I think Slack64-Current is multi lib with no 32 libs yet.
I think you can add them as you need them because there is a place for them.

what's the extent of 'multilib' ready. Does that mean 32 and 64 bit versions of standard c lib have been installed? or does it simply mean that /usr/lib and /usr/lib64 are set up?

If it's simply the directories then you would need to understand exactly what dependencies that your 32 bit app needs... no?

lumak;
I'm guna find out tonight.
I installed an extra Slack64 system to play with an I going to take a shot at gnucash which has over 20+ deps.
I also have a Slamd64 system that I can "try" to steel libs from.

I think currently it's just /usr/lib64 and that's it, no 32-bit compat libs included.

I had a play and downloaded the ia32 compatibility libraries from Slamd64 and they allowed me to install and run 32bit wine.

samac

samac:
Thant sounds like a good place for me to start.

slackass... if you get gnucash to install on slackware64, you will be a god. I just wish there was some way to statically include all the gnome dependencies into gnucash AND to install it into /opt WITH gconf bundled up so that it doesn't pollute my /etc

lumak:
I just copied my Slack64 pkg tester system to another drive so I can do multiple "hi-speed bork>hose>reloads" :-)
Don't know if I can do it but I'll give 'er hell.
My linux learnin' is similar to the way a monkey learns to get a banana by pushing the yellow button.

so:
Off to the yellow button I go! :-)

Update to wine in Slackware64-current, you only need the following Slamd64 packages samac

:/ I know slamd64 is a slackware port... but isn't mixing packages a bit on the risky side? At the VERY LEAST, we should at least recompile the slamd64 package for slackware64. Of course you all know this already, but anybody reading in my not. Also I jumped my schedule last night and shrunk my archive partition to install slackware64 :D The /lib and /usr/lib do have some files in there but I didn't look too deeply into it to see what they were, I was in a rush.


Offtopic:
I'm surprised at how resizing actually isn't that hard if you have plenty of spare room and don't have to get the math on the bit/sector conversions exactly right. Shrunk the reiserfs file system by -30G, then repartitioned for a 25G at the end of it, then resized the filesystem again to fill the extra 5Gs. Reiserfs is just old now though... I used ext4 for slackware64 partition :)

Try growing reiserfs :(

samac

haha, only if I didn't care about the data on the partition I was growing over ;)

I don't pretend to be well-versed in understanding the differences between 32-bit and 64-bit operating systems. Therefore I'll ask the question:

Do I have to reformat my disk partitions to use 64-bit?

is this an official 64bit version of slackware or a 64bit build done by some on else ??????????