On Sun, Aug 13, 2006 at 11:49:08AM -0500, Steve Jones wrote: > > So what are the pro's and con's on multi-lib vs. pure 64 bit installs? > The point of pure64 is to keep things simple - libraries in /lib, so you can mostly follow blfs instructions (a few packages need extra patches, or -fPIC passed to them, or updated config.guess and config.sub, whether you go for pure64 or multilib). The benefit is that everything uses the extra registers, and runs faster at the cost of a small increase in executable size. The downside is that you cannot run 32-bit binaries (primarily, plugins) so no realplayer, no flash, and perhaps fewer av codecs available. And probably no OOo.
Multilib needs a different mindset when you get to blfs - basically, you need to be reasonably familiar with what each package is going to install, and know what you hope to achieve. You need to work out which apps have to be built as 32-bit, and fulfil their dependencies with 32-bit libraries, and then you can let everything else build as 64-bit. The fun comes from making sure that libraries are installed into the correct directory (/lib or /lib64), ditto pkgconfig files, and persuading the 32-bit stuff to build (packages using libtool may try to link against 64-bit libs - mainly, use LDFLAGS or LDEMULATION, see the comment on 'make check' for the 32-bit libtool build in the multilib book. The gtk/pango area is also "interesting" if you have both sizes of gtk. Ken -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
