My thoughts on Slackware, life and everything

Tag: multilib (Page 3 of 9)

Cleanups from the -current update fallout

blueSW-64pxI think I have managed to fix most of the important breakage in my packages, after Slackware-current updated its icu4c package a couple of days ago.

Recompiled packages are now available for -current:

  • Regular packages: LibreOffice 5.0.3
  • KDE 5_15.11 packages: qt5 (which was bumped to 5.5.1 at the same time), step, akonadi4, akonadi, akonadi-search, akonadi-calendar and kdepimlibs. Here at home, Plasma 5 works again on latest slackware-current.
  • Multilib: fixed convertpkg-compat32 script so that it will properly handle the new eudev; and also updated the “compat32” package directory with a new eudev-compat32 package.

If there are other packages in my -current repository that require recompilation, please let me know!

Eric

GCC 5.2.0 multilib

I had a bit too much to do, so creating multilib versions of the new GCC compiler suite in Slackware-current was not on the top of my TODO list.

Today I finally built GCC 5.2.0_multilib packages and uploaded them to the server. Along with the new compilers, I also refreshed the set of “compat32” packages which give your 32bit applications a working 32bit support layer.

All of that can be downloaded from:

Have fun! Eric

Another big update in slackware-current

Fire in the hole! Damn the torpedoes.

With 281 new lines in the ChangeLog.txt, this update to slackware-currrent can be called a big one.

But the real interesting stuff is not just those sheer number of updated packages – it’s the new 4.1.6 Linux kernel, the gcc 4.9.3 compiler suite, glibc 2.22 C libraries, mesa 10.6.4,  a new libepoxy package which was required to get glamor 1.0.0 into the xorg-server… exciting times for the adventurous who are running slackware-current!

A note about mesa: it refuses to compile on 32-bit Slackware unless the ARCH is set to i586… gone is the i486 compatibility. Well, if you had watched the ChangeLog.txt these past months you’d already have noticed that updated packages  switched from i486 to i586, but that was voluntary. Mesa is the first real stumbling block.

I am in the process of upgrading my slackware64-current virtual machine and will compile new packages for the multilib gcc and glibc versions… you have to be patient a bit. You can of course go ahead and upgrade to the latest slackware-current, overwriting gcc and glibc with the official versions. All you lose is the ability to run 32-bit programs until my packages are ready. Should not take more than a day.

Pat also warned me about the upgrades to nettle and gnutls. They are likely to break many 3rd party packages because of the change in library version. Please report any broken package from my own repository, so that I can release rebuilt and fixed versions ASAP. Also, libelf was replaced with elfutils but a copy of libelf.so.0 was added to the aaa_elflibs package to keep the breakage to a minimum.

All this info is thanks to Pat who commented on this upgrade verbosely – it is background information MoZes needs for his slackwarearm, and important for my multilib.

Have fun! Eric

Rebuilt multilib gcc compiler suite for slackware-current

There were many updates for Slackware-current last night. One of them was a rebuilt gcc compiler suite, and therefore an updated multilib compiler set was due as well.

The new multilib gcc packages are now online, The set of 32-bit “compat32” packages for slackware64-current has also been refreshed. The gcc packages had to be rebuilt because of other package updates causing library version bumps, but Pat took the opportunity to add two shell scripts “c89” and “c99” that are part of POSIX standard – they call the compiler with additional compatibility parameters. This was necessitated by the fact that recent git checkouts of the VLC mediaplayer would not compile on Slackware because the VLC developers started enforcing a check on the availability of the “c99” command.

You can obtain the updated multilib packages from the URLs below or from any other mirror near you that carries copies of my repositories:

A refresher on “multilib” for new users of Slackware: if you want to use (binary-only) 32-bit software on a 64-bit Slackware installation then that is not possible out of the box, because Slackware64 is a pure 64-bit OS. You need to expand the OS with “multilib capability” so that the OS can run (and compile) 32-bit programs as well. Examples of 32-bit (closed-source) programs are Skype, Valve’s Steam Client, the WINE emulator, the Pipelight browser plugin, Citrix client etc.

Instructions on how to add or update multilib on your 64-bit Slackware can be found on the Slackware Documentation Project. Also, the slackpkg+ extension to Slackware’s own slackpkg contains the script “setupmultilib.sh” which can help you in setting up multilib properly. With slackpkg+ it is then trivial to keep your multilib installation up to date when updates occur.

Security tip:

One note on the side about last night’s Slackware -current update. The work on this update was supposed to take a while longer because Pat wants to update additional packages and a proper integration is important so that things don’t break due to library incompatibilities. But the update to the mozilla-firefox package addresses a serious and critical security issue. This security fix needed to get out to you people as fast as possible. The exploit (which was found in the wild by an attentive Firefox user and then reported to Mozilla) uses Firefox’s internal PDF viewer implementation to gain access to your local files, and uploads e.g. your ssh configuration and keys, the password file, pidgin and psi configuration files to a Russian server – pretty sensitive things.

If you have been using Firefox 38 or 39 (normal or ESR versions) on your Linux computer and visited dodgy sites recently, and you have ssh keys for accessing remote servers without a password, you may want to consider replacing these ssh keys with fresh ones.

Enjoy! Eric

Multilib gcc updated to address changes in slackware-current

slackware_multilib

In slackware-current two inter-related packages were updated yesterday: libmpc and gcc. It turns out that the update of libmpc caused a library version change. Since the gcc compiler is dynamically linked to libmpc, the gcc packages had to be recompiled in order to make it link against the new libmpc.so.3 library. Another reason for recompiling the gcc package was the missing libiberty.a file. The gcc.SlackBuild needed an additional configuration parameter to make it install into the package again.

Unfortunately that slackware-current update broke the multilib gcc packages which I have in my own repository, as several people noticed … the quick’n’dirty fix was (cd /usr/lib64 ; ln -s libmpc.so.3 libmpc.so.2).

I have recompiled the multilib gcc twice (after applying Slackware’s updates to the gcc-multilib.SlackBuild): first compilation was done with that symlink created like I just described. That resulted in the desired linkage to the new libmpc.so.3 library. Then I removed the symlink which I had created earlier and compiled the gcc packages again, just to be sure (for Slackware, this double compilation was performed as well).

The new gcc packages are now online, along with an update to the massconvert32.sh script which is part of the compat32-tools package. Also I refreshed the set of 32-bit “compat32” packages which I create from the official 32-bit Slackware package tree, because there were several updated packages in Slackware (again), and I added the libva-intel-driver-compat32 package on request.

Here is where you can find the updated packages:

If you wonder what this multilib is all about: it is needed if you want to use (binary-only) 32-bit software on 64-bit Slackware. Examples of that are Skype, Valve’s Steam Client, the WINE emulator, the Pipelight browser plugin, Citrix client etc.

Instructions on how to add or update multilib on your 64-bit Slackware can be found on the Slackware Documentation Project. Also, the slackpkg+ extension to Slackware’s own slackpkg contains the script “setupmultilib.sh” which can help you in setting up multilib properly.

 

Enjoy! Eric

PS: The nice graphic at the top was taken from the page http://gnu-linux-slackware.blogspot.nl/2013/01/switch-to-multilib-with-32-bit.html which is a Slackware related blog by Ismail.

« Older posts Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑