SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Running an update of multilib now...which mirror are you using? It could not be synced yet.
Yep, same error, here.
Looking in the archive, the doinst.sh script is cut off. the aaa_libraries package in the 32-bit slackware archive has the full one. Convert aaa_libraries manually and reinstall?
Heard back from Alien Bob...it's already fixed and will be updated when the multilib refreshes. It's harmless.
The tools package upgraded this morning but the aaa_libs package wasn't avaialble yet.
Thanks for the quick reply.
(I have a very slow internet connection, <2 MB/s, so I don't use rsync to a local repo)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,110
Original Poster
Rep:
Alienbob has been kind enough to refreshed his *compat32 packages.
Quote:
+--------------------------+
Sun Mar 5 15:47:26 UTC 2023
15.0/slackware64-compat32: Refreshed the *compat32 packages.
current/slackware64-compat32: Refreshed the *compat32 packages.
Sat Mar 11 18:28:45 UTC 2023
current/compat32-tools-3.10-noarch-4alien.tgz: in massconvert32.sh
added a/openssl11-solibs .
current/slackware64-compat32: Refreshed the *compat32 packages.
Thu Aug 3 19:38:06 UTC 2023
15.0/slackware64-compat32: Refreshed the *compat32 packages.
current/gcc-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-g++-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-gdc-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-gfortran-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-gm2-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-gnat-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-go-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/gcc-objc-13.2.0_multilib-x86_64-1alien.txz: Upgraded.
current/slackware64-compat32: Refreshed the *compat32 packages.
Caveat that it can take a bit for servers to sync. (This should fix the kde problems people are having on current...)
How does the compiler cause problems with kde. I am a bit confused. I use multilib but, for several years now I use the gcc's that come with slackware64-current rather than the multilib gcc packages. I have zero plans on compiling 32-bit on this computer. I have no issues with kde or compiling. Thanks.
How does the compiler cause problems with kde. I am a bit confused. I use multilib but, for several years now I use the gcc's that come with slackware64-current rather than the multilib gcc packages. I have zero plans on compiling 32-bit on this computer. I have no issues with kde or compiling. Thanks.
I'm not entirely sure, but apparently it was causing an issue when KDE updated and gcc didn't? I wouldn't think it would be the case, since it's still compiled against the same version of glibc as before. When gcc or glibc updates, I hold off on updating until multilib's been updated.
libstdc++.so.6 comes with the gcc-g++ package. The latest kde packages in -current were then built against the latest libstdc++.so.6 which the previous multilib gcc did not yet have.
The libstdc++.so.6 is also part of aaa_libraries package. Otherwise Slackware would at runtime depend on a compiler package.
I assume that Patrick has forgotten to refresh the libstdc++ library files in that aaa_libraries package.
I'm not entirely sure, but apparently it was causing an issue when KDE updated and gcc didn't? I wouldn't think it would be the case, since it's still compiled against the same version of glibc as before. When gcc or glibc updates, I hold off on updating until multilib's been updated.
Thanks. If I am understanding this correctly, the issue is with KDE updating and the multilib gcc packages not updating? Specifically related to, as Petri points out libstdc++.so.6; which is a run time dependency?
Before I decided to stick with the slackware64-current packages vice multilib for the gcc packages, I used to wait until multilib gcc packages were updated. The only time I do that now is if glibc is updated in slackware64-current.
I use slackpkg with slackpkg+, if glibc is updated in slackware64-current, those packages are not upgraded since multilib has priority. That said I normally wait to upgrade until the glibc multilib packages are updated. As for gcc, I give slackware64 priority so those packages are upgraded when slackware64's packages are updated.
Since it is very unlikely I will ever compile 32-bit on this computer I don't see the point in using the multilib gcc packages. It hasn't given me problems in the several years I've been doing this.
The only reason I have multilib installed in the first place is for Steam.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
If I am understanding this correctly, the issue is with KDE updating and the multilib gcc packages not updating? Specifically related to, as Petri points out libstdc++.so.6; which is a run time dependency? 
