Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
slackware:multilib [2017/07/01 21:04 (UTC)] alienbob Updated glibc packages in Slackware 14.2 and -current. |
slackware:multilib [2019/12/04 20:50 (UTC)] (current) alienbob [The quick 'n' dirty instructions] Be more specific about releases. |
||
|---|---|---|---|
| Line 89: | Line 89: | ||
| * 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!\\ 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> | + | <note warning>If you use a package manager like //slackpkg// on Slackware releases older dan 13.37 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 | [0-9]+alien | ||
| [0-9]+compat32 | [0-9]+compat32 | ||
