| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| slackware:multilib [2016/08/12 22:21 (UTC)] – New glibc 2.24 and gcc 5.4.0 in slackware-current. alienbob | slackware:multilib [2016/08/13 11:52 (UTC)] – Make the compat32-tools stand out a bit more. alienbob |
|---|
| * glibc-solibs-2.24_multilib-x86_64-1alien.txz | * glibc-solibs-2.24_multilib-x86_64-1alien.txz |
| |
| There is one additional package that you install using the "installpkg" program: | ====All releases of Slackware==== |
| | |
| | There is one additional package that you need to install using the "installpkg" program. The actual version may vary for each release of Slackware, but the package can be found in the same directory where you also find the multilib versions of ''gcc'' and ''glibc'': |
| |
| * The "32bit toolkit" (scripts that facilitate the creation of 32bit packages) | * The "32bit toolkit" (scripts that facilitate the creation of 32bit packages) |
| * compat32-tools-3.7-noarch-1alien.tgz | * compat32-tools-3.7-noarch-1alien.tgz |
| |
| <note>Slamd64 had separate 64bit and 32bit gcc/glibc multilib packages.\\ However, I believe that it is cleaner to keep these essential multilib packages undivided. I followed the concept already used in Slackware64's own //binutils// package, which has 64-bit and 32-bit multilib capability bundled into one package.</note> | |
| |
| |
| ===== Acknowledgements ===== | ===== Acknowledgements ===== |
| |
| * A lot of thanks should go to Fred Emmott, who created Slamd64, the original unofficial 64-bit fork of Slackware. Although Slackware64 was not based on Fred's work, I still learnt most of what I know about setting up the 32-bit part of a multilib Linux from his writings that are found in Slamd64. | * A lot of thanks should go to Fred Emmott, who created Slamd64, the original unofficial 64-bit fork of Slackware. Although Slackware64 was not based on Fred's work, I still learnt most of what I know about setting up the 32-bit part of a multilib Linux from his writings that are found in Slamd64.\\ Note that Slamd64 had separate 64bit and 32bit gcc/glibc multilib packages. However, I believe that it is cleaner to keep these essential multilib packages undivided. I followed the concept already used in Slackware64's own //binutils// package, which has 64-bit and 32-bit multilib capability bundled into one package. |
| |
| * Cross Linux From Scratch.\\ The CLFS Wiki (http://trac.cross-lfs.org/wiki/read#ReadtheCrossLinuxFromScratchBookOnline) is a 'must-read' if you want to understand how to port Linux to a new architecture. I took several ideas, concepts and patches from them when creating Slackware64 from scratch, and again when I created my multilib gcc/glibc packages from scratch (my README on this multilib-from-scratch is available in the ./source directory). | * Cross Linux From Scratch.\\ The CLFS Wiki (http://trac.cross-lfs.org/wiki/read#ReadtheCrossLinuxFromScratchBookOnline) is a 'must-read' if you want to understand how to port Linux to a new architecture. I took several ideas, concepts and patches from them when creating Slackware64 from scratch, and again when I created my multilib gcc/glibc packages from scratch (my README on this multilib-from-scratch is available in the ./source directory). |
