Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
slackware:multilib [2016/08/13 11:52 (UTC)]
alienbob Make the compat32-tools stand out a bit more. 		slackware:multilib [2019/12/04 20:50 (UTC)] (current)
alienbob [The quick 'n' dirty instructions] Be more specific about releases.
Line 7: Line 7:
     * //glibc// (i.e. a glibc that supports //running// both 32bit and 64bit binaries), and     * //glibc// (i.e. a glibc that supports //running// both 32bit and 64bit binaries), and
     * //gcc// (i.e. able to //compile// 32bit binaries as well as 64bit binaries).     * //gcc// (i.e. able to //compile// 32bit binaries as well as 64bit binaries).
-  - Then, system libraries are taken from 32bit Slackware and installed in the 64bit Slackware system which completes the process of creating a 32bit software layer. +  - Then, system libraries are taken from 32bit Slackware and installed in the 64bit Slackware system alongside their 64bit versions which completes the process of creating a 32bit compatibility software layer.
- +
-<note>Slackware for the x86_64 architecture (or "//Slackware64//" for short) is a pure 64-bit Operating System, but easily upgradable to multilib. //Out of the box, Slackware64 is only capable of compiling and running 64bit binaries.//</note>+
  
 When Slackware64 was released, it had an advantage over the 64bit "forks" that existed out there. These forks added the 32bit compatibility layer by recompiling a lot of their packages as 32bit binaries. Slackware on the other hand, is a distribution that consists of a 32bit and 64bit release, both of which are being developed in parallel. This means, that you do not have to compile 32-bit packages from scratch in order to add multilib capability to the 64bit system.  You simply take them from the 32-bit Slackware package tree! \\  This was one of the reasons for not adding full multilib to Slackware64 - we create the right preconditions but require the user to act if she needs multilib. \\ In a [[#detailed_instructions | section further down]], I will explain how you can take a 32-bit Slackware package (say, the "mesa" package) and re-package its content into a "mesa-compat32" package that you can install straight away on Slackware64. When Slackware64 was released, it had an advantage over the 64bit "forks" that existed out there. These forks added the 32bit compatibility layer by recompiling a lot of their packages as 32bit binaries. Slackware on the other hand, is a distribution that consists of a 32bit and 64bit release, both of which are being developed in parallel. This means, that you do not have to compile 32-bit packages from scratch in order to add multilib capability to the 64bit system.  You simply take them from the 32-bit Slackware package tree! \\  This was one of the reasons for not adding full multilib to Slackware64 - we create the right preconditions but require the user to act if she needs multilib. \\ In a [[#detailed_instructions | section further down]], I will explain how you can take a 32-bit Slackware package (say, the "mesa" package) and re-package its content into a "mesa-compat32" package that you can install straight away on Slackware64.
 +
 +<note>Slackware for the x86_64 architecture (or "//Slackware64//" for short) is a pure 64-bit Operating System, but easily upgradable to multilib. //Out of the box, Slackware64 is only capable of compiling and running 64bit binaries.//</note>
  
  
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
Line 193: Line 193:
     * gcc-objc-5.3.0_multilib-x86_64-3alien.txz     * gcc-objc-5.3.0_multilib-x86_64-3alien.txz
   * The GNU libc libraries:   * The GNU libc libraries:
-    * glibc-2.23_multilib-x86_64-1alien.txz +    * glibc-2.23_multilib-x86_64-2alien.txz 
-    * glibc-i18n-2.23_multilib-x86_64-1alien.txz +    * glibc-i18n-2.23_multilib-x86_64-2alien.txz 
-    * glibc-profile-2.23_multilib-x86_64-1alien.txz +    * glibc-profile-2.23_multilib-x86_64-2alien.txz 
-    * glibc-solibs-2.23_multilib-x86_64-1alien.txz+    * glibc-solibs-2.23_multilib-x86_64-2alien.txz
  
 ====Slackware64 current==== ====Slackware64 current====
Line 203: Line 203:
  
   * The gcc compiler suite:   * The gcc compiler suite:
-    * gcc-5.4.0_multilib-x86_64-1alien.txz +    * gcc-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-g++-5.4.0_multilib-x86_64-1alien.txz +    * gcc-brig-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-gfortran-5.4.0_multilib-x86_64-1alien.txz +    * gcc-g++-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-gnat-5.4.0_multilib-x86_64-1alien.txz +    * gcc-gfortran-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-go-5.4.0_multilib-x86_64-1alien.txz +    * gcc-gnat-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-java-5.4.0_multilib-x86_64-1alien.txz +    * gcc-go-7.1.0_multilib-x86_64-2alien.txz 
-    * gcc-objc-5.4.0_multilib-x86_64-1alien.txz+    * gcc-objc-7.1.0_multilib-x86_64-2alien.txz
   * The GNU libc libraries:   * The GNU libc libraries:
-    * glibc-2.24_multilib-x86_64-1alien.txz +    * glibc-2.25_multilib-x86_64-3alien.txz 
-    * glibc-i18n-2.24_multilib-x86_64-1alien.txz +    * glibc-i18n-2.25_multilib-x86_64-3alien.txz 
-    * glibc-profile-2.24_multilib-x86_64-1alien.txz +    * glibc-profile-2.25_multilib-x86_64-3alien.txz 
-    * glibc-solibs-2.24_multilib-x86_64-1alien.txz+    * glibc-solibs-2.25_multilib-x86_64-3alien.txz 
 + 
 +<note>Since the update to gcc 7, there is no more ''gcc-java'' package because its development has ceased.</note> 
 +<note>The ''glibc-zoneinfo'' package is not a part of multilib, since it does not contain code.  You need to install Slackware's stock ''glibc-zoneinfo'' package.</note>
  
 ====All releases of Slackware==== ====All releases of Slackware====
Line 332: Line 335:
 libtool libtool
 llvm llvm
 +opencl-headers
  
 # The L/ series: # The L/ series:
  
 +SDL2
 alsa-lib alsa-lib
 alsa-oss alsa-oss
Line 345: Line 350:
 esound esound
 expat expat
 +ffmpeg
 fftw fftw
 freetype freetype
 fribidi fribidi
 gamin gamin
 +gc
 gdk-pixbuf2 gdk-pixbuf2
 giflib giflib
Line 359: Line 366:
 gst-plugins-good gst-plugins-good
 gst-plugins-good0 gst-plugins-good0
 +gst-plugins-libav
 gstreamer gstreamer
 gstreamer0 gstreamer0
Line 366: Line 374:
 jasper jasper
 json-c json-c
 +lame
 lcms lcms
 lcms2 lcms2
Line 371: Line 380:
 libart_lgpl libart_lgpl
 libasyncns libasyncns
 +libclc
 +libedit
 libelf libelf
 libexif libexif
Line 383: Line 394:
 libmpc libmpc
 libnl3 libnl3
 +libnotify
 libogg libogg
 libpcap libpcap
Line 391: Line 403:
 libtermcap libtermcap
 libtiff libtiff
 +libunistring
 libusb libusb
 libvorbis libvorbis
Line 397: Line 410:
 lzo lzo
 ncurses ncurses
 +ocl-icd
 openjpeg openjpeg
 orc orc
Line 402: Line 416:
 popt popt
 pulseaudio pulseaudio
 +python-six
 qt qt
 readline readline
Line 425: Line 440:
 openssl openssl
 p11-kit p11-kit
 +samba
  
 # The X/ series: # The X/ series:
Line 448: Line 464:
 libXfixes libXfixes
 libXfont libXfont
 +libXfont2
 libXfontcache libXfontcache
 libXft libXft
Line 470: Line 487:
 libepoxy libepoxy
 libfontenc libfontenc
 +libinput
 libpciaccess libpciaccess
 libva libva
Line 478: Line 496:
 mesa mesa
 pixman pixman
 +vulkan-sdk
 xcb-util xcb-util
  
Line 493: Line 512:
   * [[http://slackware.com/~alien/multilib/ | http://slackware.com/~alien/multilib/]]   * [[http://slackware.com/~alien/multilib/ | http://slackware.com/~alien/multilib/]]
   * [[http://bear.alienbase.nl/mirrors/people/alien/multilib/ | http://bear.alienbase.nl/mirrors/people/alien/multilib/]]   * [[http://bear.alienbase.nl/mirrors/people/alien/multilib/ | http://bear.alienbase.nl/mirrors/people/alien/multilib/]]
-  * [[http://slackware.org.uk/people/alien/multilib/| http://slackware.org.uk/people/alien/multilib/]]+  * [[http://slackware.uk/people/alien/multilib/| http://slackware.uk/people/alien/multilib/]]
   * [[http://alien.slackbook.org/slackware/multilib/| http://alien.slackbook.org/slackware/multilib/]]   * [[http://alien.slackbook.org/slackware/multilib/| http://alien.slackbook.org/slackware/multilib/]]
   * [[http://slackbuilds.org/mirror/alien/multilib/| http://slackbuilds.org/mirror/alien/multilib/]]   * [[http://slackbuilds.org/mirror/alien/multilib/| http://slackbuilds.org/mirror/alien/multilib/]]
 +
 +
 ===== 3rd party support tools ===== ===== 3rd party support tools =====
  

In Other Languages
QR Code
QR Code slackware:multilib (generated for current page)