| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| slackware:multilib [2009/10/19 07:55] – Add link tp pt_br translation. alien | slackware:multilib [2012/05/03 08:18] – Use full hostname connie.slackware.com alien |
|---|
| I will give some examples of programs that require multilib support on a 64bit Slackware because they will not start or compile on Slackware64 without the 32bit compatibility layer: | I will give some examples of programs that require multilib support on a 64bit Slackware because they will not start or compile on Slackware64 without the 32bit compatibility layer: |
| * [[http://winehq.org/ | Wine]] \\ Most Windows programs are still 32bit, and in order to run those on Linux with Wine, you need a 32bit version of Wine. | * [[http://winehq.org/ | Wine]] \\ Most Windows programs are still 32bit, and in order to run those on Linux with Wine, you need a 32bit version of Wine. |
| | * [[http://www.virtualbox.org/ | VirtualBox]] \\ The popular virtual machine software. Although this is (partly) open source it still needs 32-bit compatibility libraries on 64-bit Slackware. |
| * [[http://www.skype.com/ | Skype]], [[http://www.citrix.com/lang/English/home.asp | Citrix client]], ... \\ These programs are proprietary and closed-source. We have to depend on the developer to make 64bit binaries available. So far, that has not happened for these example programs. | * [[http://www.skype.com/ | Skype]], [[http://www.citrix.com/lang/English/home.asp | Citrix client]], ... \\ These programs are proprietary and closed-source. We have to depend on the developer to make 64bit binaries available. So far, that has not happened for these example programs. |
| |
| ===== Obtaining multilib packages ===== | ===== Obtaining multilib packages ===== |
| |
| You can download a set of multilib-enabled packages and scripts from my web site: http://slackware.com/~alien/multilib/ . | You can download a set of multilib-enabled packages and scripts from my web site: http://connie.slackware.com/~alien/multilib/ . |
| |
| The packages are accompanied by sources and SlackBuild scripts, plus several README files (this Wiki article is based on one of these READMEs). The //only// required downloads are the binary packages in the toplevel directory. The rest is available for educational purposes. | Apart from several README files (this Wiki article is based on one of these READMEs), you will find one subdirectory for every 64-bit Slackware release below the toplevel directory "//multilib//". There is another directory called "source". The "//source//" directory contains package sources and SlackBuild scripts.\\ The stuff that you are really interested in - the binary packages - is available in the //<slackware_release_number>// directory below the toplevel directory. Every such directory also contains a "//slackware64-compat32//" subdirectory where you will find an essential set of converted 32-bit Slackware packages, ready for installing on your 64-bit Slackware. |
| | |
| | <note tip>In order to keep up to date, I advise you to keep an eye on the [[http://connie.slackware.com/~alien/multilib/ChangeLog.txt | ChangeLog]] I keep for my multilib packages. Usually, I will have //updated glibc and gcc// packages available within a day after Slackware has updates to gcc and glibc. Also check out [[#rd_party_support_tools | compat32pkg]] by Sėbastien Ballet which automates this process, similar to slackpkg.</note> |
| |
| |
| upgradepkg --reinstall --install-new *.t?z | upgradepkg --reinstall --install-new *.t?z |
| </code> in the directory where you downloaded them.\\ This command will also install an additional package called "//compat32-tools//". | </code> in the directory where you downloaded them.\\ This command will also install an additional package called "//compat32-tools//". |
| * You must have a 32-bit Slackware package tree available. Those who bought an official Slackware 13.0 DVD can simply use that DVD: it is dual-sided and 32bit Slackware is on one of the sides. For the sake of this example I will assume that a 32bit Slackware directory tree is available at "''~ftp/pub/slackware/slackware-13.0/slackware/''".\\ There should be sub-directories called 'a', 'ap', 'd', 'l', 'n', 'x' immediately below this directory. | * If you also downloaded a directory called //slackware64-compat32// then you are lucky, because I did the 32bit package conversion for you already! All you do is run the command: <code> |
| * Create a new empty directory (let us call it 'compat32') and change into it: <code> | upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z |
| mkdir compat32 ; cd compat32 | </code> which will install all the converted 32-bit Slackware packages (or upgrade them if you already had installed older multilib packages, for instance when you are upgrading to a newer Slackware). That's all! |
| | * If you can't find that subdirectory called //slackware64-compat32// then you have to do the conversion yourself. Not difficult at all, it takes a few minutes: |
| | * The fastest is if you have a local directory with original 32-bit Slackware packages available (also called a //local mirror//). Those who bought an official Slackware DVD can simply use that DVD: it is dual-sided and 32bit Slackware is on one of the sides. __For the sake of this example__ I will assume that you have a local 32bit Slackware directory tree available at "''/home/ftp/pub/slackware/slackware-13.37/slackware/''".\\ There should be sub-directories called 'a', 'ap', 'd', 'l', 'n', 'x' immediately below this directory. (If you have mounted a Slackware DVD, your directory will probably be "''/media/SlackDVD/slackware/''" but I will not use that in the example commands below). |
| | * Create a new empty directory (let us call it 'slackware64-compat32') and change into it: <code> |
| | mkdir slackware64-compat32 ; cd slackware64-compat32 |
| </code> | </code> |
| * Run the following command to create a set of 32bit compatibility packages, using the original 32bit Slackware packages as input: <code> | * Run the following command to create a set of 32bit compatibility packages, using the directory to the official 32bit Slackware packages as input: <code> |
| massconvert32.sh -i ~ftp/pub/slackware/slackware-13.0/slackware/ | massconvert32.sh -i /home/ftp/pub/slackware/slackware-13.37/slackware/ |
| </code> | </code> |
| * Install the 60 MB of freshly converted 32-bit Slackware packages: <code> | * The previous step takes a while. When it ends, proceed to install the 90 MB of freshly converted 32-bit Slackware packages which were created in subdirectories below your //current directory//: <code> |
| installpkg *-compat32/*.t?z | upgradepkg --install-new *-compat32/*.t?z |
| </code> | </code> |
| * Done! You can now start downloading, installing and running 32bit programs. | * Done! You can now start downloading, installing and running 32bit programs. This was not so hard, was it? |
| |
| <note warning>If you use a package manager like //slackpkg// you will have to add ''glibc'' and ''gcc'' to it's package blacklist. If you do not take this precaution, you run the risk of your package manager accidentally replacing the new multilib versions with Slackware's original pure-64bit versions!</note> | <note warning>If you use a package manager like //slackpkg// you will have to add all the ''glibc'' and ''gcc'' package names to its package blacklist. If you do not take this precaution, you run the risk of your package manager accidentally replacing your multilib versions with Slackware's original pure 64-bit versions!\\ If you run Slackware 13.37 or newer, then slackpkg supports regular expressions in the blacklist file. In that case, a single line in ''/etc/slackpkg/blacklist'' will be enough to blacklist all of my packages (including multilib gcc and glibc packages and all ''compat32'' packages): <code>[0-9]+alien</code></note> |
| | |
| | <note tip>If you are running Slackware 13.1 or newer, and downloaded the compat32-tools package for that release, the //massconvert32.sh// script can use a remote webserver to download the 32-bit Slackware packages from, instead of requiring a local Slackware mirror or a DVD. You use the "-u" parameter to specify the remote URL like this: <code>massconvert32.sh -u http://someserver.org/path/to/slackware-13.37/slackware</code> </note> |
| |
| |
| === Upgrading glibc and gcc === | === Upgrading glibc and gcc === |
| |
| The following glibc/gcc packages are replacements for - not additions to - standard Slackware packages. You use the "upgradepkg" program to upgrade to my multilib versions of gcc and glibc. You will need these in order to run (glibc), and build (gcc), 32-bit software on your 64-bit Slackware computer (the package versions shown below are for Slackware 13.0): | The following glibc/gcc packages are replacements for - not additions to - standard Slackware packages. You use the "upgradepkg" program to upgrade to my multilib versions of gcc and glibc. You will need these in order to run (glibc), and build (gcc), 32-bit software on your 64-bit Slackware computer: |
| | |
| | ====Slackware64 13.0==== |
| |
| * The gcc compiler suite: | * The gcc compiler suite: |
| * glibc-solibs-2.9_multilib-x86_64-3alien.txz | * glibc-solibs-2.9_multilib-x86_64-3alien.txz |
| * glibc-zoneinfo-2.9_multilib-noarch-3alien.txz | * glibc-zoneinfo-2.9_multilib-noarch-3alien.txz |
| | |
| | ====Slackware64 13.1==== |
| | |
| | * The gcc compiler suite: |
| | * gcc-4.4.4_multilib-x86_64-1alien.txz |
| | * gcc-g++-4.4.4_multilib-x86_64-1alien.txz |
| | * gcc-gfortran-4.4.4_multilib-x86_64-1alien.txz |
| | * gcc-gnat-4.4.4_multilib-x86_64-1alien.txz |
| | * gcc-java-4.4.4_multilib-x86_64-1alien.txz |
| | * gcc-objc-4.4.4_multilib-x86_64-1alien.txz |
| | |
| | * The GNU libc libraries: |
| | * glibc-2.11.1_multilib-x86_64-3alien.txz |
| | * glibc-i18n-2.11.1_multilib-x86_64-3alien.txz |
| | * glibc-profile-2.11.1_multilib-x86_64-3alien.txz |
| | * glibc-solibs-2.11.1_multilib-x86_64-3alien.txz |
| | * glibc-zoneinfo-2.11.1_multilib-noarch-3alien.txz |
| | |
| | ====Slackware64 13.37==== |
| | |
| | * The gcc compiler suite: |
| | * gcc-4.5.2_multilib-x86_64-2alien.txz |
| | * gcc-g++-4.5.2_multilib-x86_64-2alien.txz |
| | * gcc-gfortran-4.5.2_multilib-x86_64-2alien.txz |
| | * gcc-gnat-4.5.2_multilib-x86_64-2alien.txz |
| | * gcc-java-4.5.2_multilib-x86_64-2alien.txz |
| | * gcc-objc-4.5.2_multilib-x86_64-2alien.txz |
| | |
| | * The GNU libc libraries: |
| | * glibc-2.13_multilib-x86_64-3alien.txz |
| | * glibc-i18n-2.13_multilib-x86_64-3alien.txz |
| | * glibc-profile-2.13_multilib-x86_64-3alien.txz |
| | * glibc-solibs-2.13_multilib-x86_64-3alien.txz |
| | * glibc-zoneinfo-2.13_multilib-noarch-3alien.txz |
| | |
| | ====Slackware64 current==== |
| | |
| | * As long as you don't see a separate directory named "//current//" you can just use the files in the directory for the most recent stable release. |
| | |
| | * The gcc compiler suite: |
| | * gcc-4.5.3_multilib-x86_64-2alien.txz |
| | * gcc-g++-4.5.3_multilib-x86_64-2alien.txz |
| | * gcc-gfortran-4.5.3_multilib-x86_64-2alien.txz |
| | * gcc-gnat-4.5.3_multilib-x86_64-2alien.txz |
| | * gcc-java-4.5.3_multilib-x86_64-2alien.txz |
| | * gcc-objc-4.5.3_multilib-x86_64-2alien.txz |
| | |
| | * The GNU libc libraries: |
| | * glibc-2.13_multilib-x86_64-5alien.txz |
| | * glibc-i18n-2.13_multilib-x86_64-5alien.txz |
| | * glibc-profile-2.13_multilib-x86_64-5alien.txz |
| | * glibc-solibs-2.13_multilib-x86_64-5alien.txz |
| | * glibc-zoneinfo-2.13_multilib-noarch-5alien.txz |
| |
| There is one additional package that you install using the "installpkg" program: | There is one additional package that you install using the "installpkg" program: |
| |
| * The "32-bit toolkit" (scripts that facilitate the creation of 32bit packages) | * The "32-bit toolkit" (scripts that facilitate the creation of 32bit packages) |
| * compat32-tools-1.0-noarch-1.tgz | * compat32-tools-2.0-noarch-1alien.tgz |
| |
| <note>Slamd64 has 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> | <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> |
| |
| |
| A little bit of extra care is required so that unnecessary/unwanted files are stripped from the 32bit packages before you install them. What you need, is a 32bit package that does not conflict with whatever is already present in 64bit Slackware. Hence the name "32bit compatibility package". | A little bit of extra care is required so that unnecessary/unwanted files are stripped from the 32bit packages before you install them. What you need, is a 32bit package that does not conflict with whatever is already present in 64bit Slackware. Hence the name "32bit compatibility package". |
| |
| I decided that it would be a waste of download bandwidth if I created 32bit compatibility versions of Slackware packages myself. After all, you have probably bought the Slackware 13.0 DVD so you already possess both 64bit and 32bit versions of Slackware... or else the 32bit Slackware tree is available for free download of course ;-) | I decided that it would be a waste of download bandwidth if I created 32bit compatibility versions of Slackware packages myself. After all, you have probably bought the Slackware 13.37 DVD so you already possess both 64bit and 32bit versions of Slackware... or else the 32bit Slackware tree is available for free download of course ;-) |
| |
| Instead, I wrote a few scripts (parts of the script code were written by Fred Emmott of [[http://slamd64.com/ | Slamd64]] fame) and wrapped these into a "//compat32-tools//" package. Their purpose is to let you extract the content from any 32bit Slackware package and use that to create a new package which you can safely install on your 64bit Slackware. | Instead, I wrote a few scripts (parts of the script code were written by Fred Emmott of [[http://slamd64.com/ | Slamd64]] fame) and wrapped these into a "//compat32-tools//" package. Their purpose is to let you extract the content from any 32bit Slackware package and use that to create a new package which you can safely install on your 64bit Slackware. |
| * ///etc/profile.d/32dev.sh//\\ This is the same script that comes with Slamd64. It reconfigures your shell environment so that it will be easier for you to compile 32-bit software (by preferring the 32-bit compilers and libraries over their 64-bit versions) | * ///etc/profile.d/32dev.sh//\\ This is the same script that comes with Slamd64. It reconfigures your shell environment so that it will be easier for you to compile 32-bit software (by preferring the 32-bit compilers and libraries over their 64-bit versions) |
| |
| * //convertpkg-compat32//\\ This script takes a 32-bit Slackware package and converts it to a '-compat32' package that you can safely install (using "installpkg") on Slackware64, alongside the 64-bit version of the same software package. For instance: suppose you need 32bit libraries that are in the mesa package. You take the mesa package from 32bit Slackware (''x/mesa-7.5-i486-1.txz'') and then run <code> | * //convertpkg-compat32//\\ This script takes a 32-bit Slackware package and converts it to a '-compat32' package that you can safely install (using "installpkg") on Slackware64, alongside the 64-bit version of the same software package. For instance: suppose you need 32bit libraries that are in the mesa package. You take the mesa package from 32-bit Slackware (''x/mesa-7.5-i486-1.txz'') and then run <code> |
| convertpkg-compat32 /path/to/mesa-7.5-i486-1.txz | convertpkg-compat32 -i /path/to/mesa-7.5-i486-1.txz |
| </code> which will create a new package called ''mesa-compat32-7.5-x86_64-1.txz''. This new package (which is created in your ''/tmp'' directory unless you specified another destination) is basically the old 32bit package, but stripped from non-essential stuff. The changed basename (//mesa// becomes //mesa-compat32//) allows you to install this new package in Slackware64 where it will co-exist with the 64bit //mesa// package, not overwriting any files.\\ The script leaves temporary files in the directory "''/tmp/package-<prgnam>-compat32''" which you can safely delete. | </code> which will create a new package called ''mesa-compat32-7.5-x86_64-1.txz''. This new package (which is created in your ''/tmp'' directory unless you specified another destination) is basically the old 32bit package, but stripped from non-essential stuff. The changed basename (//mesa// becomes //mesa-compat32//) allows you to install this new package in Slackware64 where it will co-exist with the 64bit //mesa// package, not overwriting any files.\\ The script leaves temporary files in the directory "''/tmp/package-<prgnam>-compat32''" which you can safely delete. |
| |
| * //massconvert32.sh//\\ This script contains an internal list of what I consider the essential subset of 32-bit Slackware packages. It uses the above "//convertpkg-compat32//" script to grab every package that is on this internal list, and convert these into '-compat32' packages.\\ You need to run this script only once, for example like this (the example assumes that you mounted your 32bit Slackware DVD on ''/mnt/dvd''): <code> | * //massconvert32.sh//\\ This script contains an internal list of what I consider the essential subset of 32-bit Slackware packages. It uses the above "//convertpkg-compat32//" script to grab every package that is on this internal list, and convert these into '-compat32' packages.\\ You need to run this script only once, for example like this (the example assumes that you mounted your 32bit Slackware DVD on ''/mnt/dvd''): <code> |
| massconvert32.sh -i /mnt/dvd/slackware -d ~/compat32 | massconvert32.sh -i /mnt/dvd/slackware -d ~/compat32 |
| </code> This action will result in about 60 MB of new packages which you will find inside the newly created directory ''~/compat32'' (the directory's name is arbitrary of course, I chose it for the sake of this example). These packages comprise the 32bit component of your multilib Slackware64 system.\\ They should be installed using "installpkg", and they give you a pretty complete 32-bit compatibility layer on top of Slackware64: <code> | </code> This action will result in about 60 MB of new packages which you will find inside the newly created directory ''~/compat32'' (the directory's name is arbitrary of course, I chose it for the sake of this example). These packages comprise the 32bit component of your multilib Slackware64 system.\\ They should be installed using "''installpkg''", and they give you a pretty complete 32-bit compatibility layer on top of Slackware64: <code> |
| installpkg ~/compat32/*/*.t?z | installpkg ~/compat32/*/*.t?z |
| </code> | </code> If you are upgrading from an earlier version of these packages (because for instance you upgraded your 64-bit Slackware to a newer release) then you do not use "''installpkg''" of course, but "''upgradepkg --install-new''" instead: <code> |
| | upgradepkg --install-new ~/compat32/*/*.t?z |
| | </code> The "//--install-new//" parameter is needed to install the new //''compat32''// packages which were added between releases. |
| |
| <note important>When installing the //''compat32''// packages you will notice that some will show errors about missing files in ''/etc''. This is "by design", and these errors can be ignored. These messages are caused by the fact that files in ''/etc'' are removed from a "-compat32" package during conversion (except for //pango// and //gtk+2//). I assume that files in ''/etc'' will already have been installed by the original 64bit packages.\\ An example of these "errors" for the ''cups-compat32'' package: <code> | <note important>When installing the //''compat32''// packages you will notice that some will show errors about missing files in ''/etc''. This is "by design", and these errors can be ignored. These messages are caused by the fact that files in ''/etc'' are removed from a "-compat32" package during conversion (except for //pango// and //gtk+2//). I assume that files in ''/etc'' will already have been installed by the original 64bit packages.\\ An example of these "errors" for the ''cups-compat32'' package: <code> |
| |
| In this changed environment, you will be able to use standard SlackBuilds to build 32-bit packages for Slackware64. There are two things to keep in mind: | In this changed environment, you will be able to use standard SlackBuilds to build 32-bit packages for Slackware64. There are two things to keep in mind: |
| - You will have to define the ARCH variable as 'x86_64' even though you are compiling a 32-bit program! | - You will have to define the ARCH variable as 'x86_64' even though you are compiling a 32-bit program! \\ This is related to the //triplet// of "$ARCH-slackware-linux" which is normally used in the "configure" command. Also, try setting the ARCH to for instance "i486" and you will see that the //CFLAGS// definition for that architecture will result in gcc errors like "//compiler can not create executables//". This is related to the design of a SlackBuild script. Rather than editing the script and change/remove //CFLAGS// definitions, you can set the ARCH to "x86_64" and save yourself some time. The real work is being done by the 32dev.sh script. |
| - You will have to edit the SlackBuild and if it wants to use 'lib64/' directories for "$ARCH = x86_64", you will have to force it to use 'lib/' directories instead. Usually, this is accomplished by finding a definition like: <code> | - You will have to edit the SlackBuild if it wants to use 'lib64/' directories for "$ARCH = x86_64". You have to force it to use 'lib/' directories instead. Usually, this is accomplished by finding a definition like: <code> |
| LIBDIRSUFFIX="64" | LIBDIRSUFFIX="64" |
| </code> and changing this line to <code> | </code> and changing this line to <code> |
| ===== Caveats ===== | ===== Caveats ===== |
| |
| After installing the "''-compat32''" packages, you may have to re-install your binary //Nvidia// or //Ati// video X.Org drivers. These driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. If you installed the driver files for both architectures, the "''mesa-compat32''" package will overwrite some of the 32bit library files. | * After installing the "''-compat32''" packages, you may have to re-install your binary //Nvidia// or //Ati// video X.Org drivers. These driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. If you installed the driver files for both architectures, the "''mesa-compat32''" package will overwrite some of the 32bit library files.\\ \\ On the other hand, if you originally //only// installed the 64bit driver libraries for your Nvidia/Ati card, it is recommended after installation of the //multilib// packages, to re-install the binary driver package. This time, choose to install the 32bit driver files as well.\\ \\ The graphical 32bit applications that you are going to run on your multilib installation will require these 32bit driver libraries. Crashes are likely to occur if you fail to install the correct files. |
| |
| On the other hand, if you originally //only// installed the 64bit driver libraries for your Nvidia/Ati card, it is recommended after installation of the //multilib// packages, to re-install the binary driver package. This time, choose to install the 32bit driver files as well. | * If you want to compile your 64bit kernel yourself, be sure to compile 32bit emulation capability into it or else multilib will mysteriously fail. You will need this piece of kernel configuration: **CONFIG_IA32_EMULATION** |
| | |
| The graphical 32bit applications that you are going to run on your multilib installation will require these 32bit driver libraries. Crashes are likely to occur if you fail to install the correct files. | |
| |
| |
| ===== Packages converted by massconvert32.sh ===== | ===== Packages converted by massconvert32.sh ===== |
| |
| This is the list of packages that is converted into "//-compat32//" versions by the ''massconvert32.sh'' script: | This is the list of packages that is converted into "//-compat32//" versions by the ''massconvert32.sh'' script. Note that some of these packages are not part of Slackware 13.0 or 13.1, they were added in a later Slackware version so they will produce a "//*** FAIL: package 'package_name' was not found!//" message when you run the script on an older release. The other way round is true as well - some packages have been //removed// in later versions of Slackware and they will also trigger the "//*** FAIL: package 'package_name' was not found!//" message. Don't worry about that. |
| |
| <code bash> | <code bash> |
| # The A/ series: | # The A/ series: |
| |
| | aaa_elflibs |
| bzip2 | bzip2 |
| cups | cups |
| e2fsprogs | e2fsprogs |
| openssl-solibs | openssl-solibs |
| | util-linux |
| |
| # The AP/ series: | # The AP/ series: |
| |
| | mpg123 |
| mysql | mysql |
| |
| alsa-oss | alsa-oss |
| atk | atk |
| | audiofile |
| cairo | cairo |
| ncurses | dbus-glib |
| | esound |
| expat | expat |
| freetype | freetype |
| gamin | gamin |
| | gdk-pixbuf2 |
| glib2 | glib2 |
| gtk+2 | gtk+2 |
| | gst-plugins-base |
| | gst-plugins-good |
| | gstreamer |
| hal | hal |
| jasper | jasper |
| lcms | lcms |
| | libart_lgpl |
| | libelf |
| libexif | libexif |
| | libglade |
| libgphoto2 | libgphoto2 |
| libjpeg | |
| libidn | libidn |
| | libieee1284 |
| | libjpeg |
| libmng | libmng |
| | libmpc |
| | libpcap |
| libpng | libpng |
| | libsndfile |
| libtermcap | libtermcap |
| libtiff | libtiff |
| | libusb |
| libxml2 | libxml2 |
| libxslt | libxslt |
| | ncurses |
| pango | pango |
| | popt |
| qt | qt |
| readline | readline |
| sdl | sdl |
| | seamonkey-solibs |
| svgalib | svgalib |
| | v4l-utils |
| zlib | zlib |
| |
| # The N/ series: | # The N/ series: |
| |
| | curl |
| cyrus-sasl | cyrus-sasl |
| gnutls | gnutls |
| |
| fontconfig | fontconfig |
| | glew |
| libFS | libFS |
| libICE | libICE |
| libdrm | libdrm |
| libfontenc | libfontenc |
| liblbxutil | |
| libxcb | libxcb |
| mesa | mesa |
| |
| |
| ===== Translations ===== | ===== 3rd party support tools ===== |
| * Bruno Russo translated this article to portuguese (brazil): http://www.brunorusso.eti.br/slackware/doku.php?id=multilib_para_o_slackware_x86_64 | |
| |
| | * Sėbastien Ballet has written a tool called //compat32pkg//. On [[http://compat32pkg.sourceforge.net/ | his web site]] he has //compat32pkg// available for download as well as extensive documentation about how to use it on Slackware64.\\ I will quote the site:\\ //"Compat32pkg is an automated tool that provides all the necessary for managing (converting, installing, upgrading, removing) the 32-bit part of AlienBob's multilib for slackware-64, and all 32-bit packages from Slackware-32 for which users could find a needs into a 64-bit environment, like firefox, seamonkey, jre,..."// |
| |
| | |
| | ===== Translations ===== |
| | |
| | * Bruno Russo translated this article to portuguese (brazil): http://www.brunorusso.eti.br/slackware/doku.php?id=multilib_para_o_slackware_x86_64 |
| | * Mehdi Esmaeelpour translated this article to persian: http://www.slack-world.com/index.php/articles/43-general-system/85-multilib-slackware64 |
| | * Patrick FONIO and Sebastien BALLET translated this article to french: http://wiki.slackware-fr.org/avance:articles:slackware64-multilib |
| ===== Acknowledgements ===== | ===== Acknowledgements ===== |
| |
