Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.
Trace:
Differences
This shows you the differences between two versions of the page.
|
slackware:multilib [2011/06/02 11:36] alien Add new package names for -current. |
slackware:multilib [2012/05/03 08:18] (current) alien Use full hostname connie.slackware.com |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| ===== 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/ . |
| 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. | 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://slackware.com/~alien/multilib/ChangeLog | 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> | + | <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> |
| Line 59: | Line 59: | ||
| * Done! You can now start downloading, installing and running 32bit programs. This was not so hard, was it? | * 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 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!</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> | <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> | ||
| Line 217: | Line 217: | ||
| ===== 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. | + | |
| Line 365: | Line 363: | ||
| * Bruno Russo translated this article to portuguese (brazil): http://www.brunorusso.eti.br/slackware/doku.php?id=multilib_para_o_slackware_x86_64 | * 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 | * 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 ===== | ||
