32bit support on 64bit Linux

[Bill Davidsen]

Don Quixote de la Mancha wrote:
>>>>> There is a single yum target, that will bring in all (or most) of the 32bit
>>>>> libraries
>>>>> and things that are needed to run 32bit applications on 64bit Fedora.
> 
> It is also possible to install just the specific 32-bit libraries that
> you need.  That's what I did when I built ZooLib for 32-bit under
> 64-bit Fedora.  (http://www.zoolib.org/)
> 
> If you're building a 32-bit program from source, just try to build it
> before installing any 32-bit libraries.  The link will fail because it
> can't find a bunch of stuff.  Try to figure out what 32-bit yum
> packages satisfy just the first few complaints, then install the
> packages and try again.
> 
> After a few rounds of this you'll have pretty close to just the bare
> minimum of libraries needed for that one program.
> 
> If you have a binary executable, and not the source, then ry running
> it.  It won't run because it can't find a bunch of libraries.  Install
> the first two or three libraries that it complains about, then Lather,
> Rinse, Repeat.
> 
I have to ask, do you find it's valuable to do all this work to save a MB or 
two? Don't take that as a criticism, I just don't see any reason to spend the 
time minimizing anymore. I find the single package to be a great time saver, 
although I don run a 32 bit system in a VM which is useful for doing 32 bit stuff.

> In general a runtime library named libfoo.so will have a yum package
> called libfoo.i386 or some such, and a development library named
> something like libfoo-dev.i386.  You only need the "-dev" libraries if
> you're developing from source - these include the header files, that
> aren't needed for runtime support.
> 
> I'll send you my bill in the mail.
> 
> Don Quixote


-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot