Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 11-13-2017, 03:14 PM   #1
LQ Newbie
Registered: Dec 2016
Location: Pennsylvania
Distribution: Slackware-x86_64
Posts: 5

Rep: Reputation: Disabled
Unhappy Multilib issues with stable 14.2

I recently grabbed multilib packages and followed all instructions (as I always do)
Then proceeded to run slackpkg update; slackpkg upgrade-all. Slackpkg listed gcc-*

Which over wrote my multilib.

Is this a problem? Should I skip slackpkg upgrade gcc-* ?? or keep the multilib?

Old 11-13-2017, 03:28 PM   #2
Alien Bob
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,259

Rep: Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371Reputation: 5371
My guess is that you did not follow the complete instructions.
See and scroll down to the note in the box with the red background.
Once of its sentences says it all:
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!
Old 11-13-2017, 03:31 PM   #3
LQ Newbie
Registered: Dec 2016
Location: Pennsylvania
Distribution: Slackware-x86_64
Posts: 5

Original Poster
Rep: Reputation: Disabled
Thank you... lack of coffee doesn't help.
Old 11-13-2017, 03:34 PM   #4
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 Multilib
Posts: 544

Rep: Reputation: 146Reputation: 146
If you are using the Slackware slackpkg, did you blacklist the alien packages which the documentation recommends to avoid the gcc multilib and the compat32 upgrades? Check AlienBob's article and read beyond the steps for adding multilib, it's explained.

Darn , AlienBob got to you before me... :-) Still look at the following and make managing your slackware system easier.

If you are using slackpkg+ then read AlienBob's article introducing slackpkg+ tells you not to blacklist and instead use repository priorities or greylist function of slackpkg+. Priorities will not show you the slackware64 gcc upgrades, and greylist will notify you of the upgrades but they will not be selected.

Hopefully this helps. Cheers, BrianA_MN

Last edited by bamunds; 11-13-2017 at 03:35 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] A few issues with version 23.0 Stable Edward4m 4MLinux 20 11-04-2017 07:30 AM
[SOLVED] DiRT Rally texture issues with Slackware64-current multilib and RX 480 Fluffy Slackware 7 07-14-2017 07:11 PM
Steam multilib Current issues - Libgl GummiWorm Slackware 5 10-09-2016 10:55 AM
[ANN] mk-slack64-multilib : A tool to create slackware64+multilib tree/iso phenixia2003 Slackware 5 12-28-2012 05:42 AM
grub issues on stable !!!!!!! blacksky2 Debian 16 01-03-2009 12:18 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:47 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration