LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-13-2018, 05:34 PM   #1
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 167
Blog Entries: 2

Rep: Reputation: 28
Adding multilib to Slack 14.2 broke all /bin commands?


So I'm adding multilib support to Slack 14.2 via the instructions from docs.slackware.com. Specifically, this:


"Download the packages from my web site (I gave you the URL in the previous section, but this example is using a mirror URL). Suppose you are running Slackware 14.2. You execute:

Code:
# SLACKVER=14.2
# mkdir multilib
# cd multilib
# lftp -c "open http://bear.alienbase.nl/mirrors/people/alien/multilib/ ; mirror -c -e ${SLACKVER}"
# cd ${SLACKVER}
Upgrade your 64bit Slackware “gcc” and “glibc” packages to my multilib versions.
Run the command

Code:
# upgradepkg --reinstall --install-new *.t?z
after you changed to the directory where you downloaded these packages.
This command will also install an additional package called “compat32-tools”."

First block seems fine, downloads everything. Then, I run

Code:
# cd 14.2/
# upgradepkg --resintall --install-new *.t?z
And it proceeds to go through a number of installations, for example:

Code:
Verifying package gcc-objc-5.5.0_multilib-x86_64-1alien.txz.
Installing package gcc-objc-5.5.0_multilib-x86_64-1alien.txz:
PACKAGE DESCRIPTION:
# gcc-objc (Objective-C support for GCC)
#
# Objective-C support for the GNU Compiler Collection.
#
# This package contains those parts of the compiler collection needed to
# compile code written in Objective-C.  Objective-C was originally
# developed to add object-oriented extensions to the C language, and is
# best known as the native language of the NeXT computer.
#
# The base gcc package is also required.
#
Executing install script for gcc-objc-5.5.0_multilib-x86_64-1alien.txz.
Package gcc-objc-5.5.0_multilib-x86_64-1alien.txz installed.

Package gcc-objc-5.5.0-i586-1_slack14.2 upgraded with new package ./gcc-objc-5.5.0_multilib-x86_64-1alien.txz.
Then, the following happens:
Code:
+==============================================================================
| Upgrading glibc-2.23-i586-4_slack14.2 package using ./glibc-2.23_multilib-x86_64-4alien.txz
+==============================================================================

Pre-installing package glibc-2.23_multilib-x86_64-4alien...
/sbin/installpkg: line 517: /sbin/ldconfig: cannot execute binary file: Exec format error
/bin/bash: line 38: sbin/ldconfig: cannot execute binary file: Exec format error
/bin/bash: line 58: /sbin/ldconfig: cannot execute binary file: Exec format error
/bin/bash: line 58: /sbin/ldconfig: cannot execute binary file: Exec format error
/bin/bash: line 58: /sbin/ldconfig: cannot execute binary file: Exec format error
...
/bin/bash: line 206: /usr/bin/ln: No such file or directory
/bin/bash: line 207: /usr/bin/rm: No such file or directory
/bin/bash: line 208: /usr/bin/ln: No such file or directory
...
/sbin/upgradepkg: /sbin/installpkg: /bin/sh: bad interpreter: No such file or directory
Package glibc-2.23-i586-4_slack14.2 upgraded with new package ./glibc-2.23_multilib-x86_64-4alien.txz.
/sbin/upgradepkg: line 178: /usr/bin/dirname: No such file or directory
And now I've basically lost a bunch of my system commands,
Code:
/multilib/14.2# ls
-su: /bin/ls: No such file or directory
/multilib/14.2# rm
-su: /usr/bin/rm: No such file or directory
/multilib/14.2# which rm
-su: /usr/bin/which: No such file or directory
/multilib/14.2# cd ..
/multilib#
So cd works, but that's kinda it. So I guess maybe the multilib packages from alienbob are not safe (although I strongly suspect I did something dumb...), but before I worry about that, does anyone have any idea how to get me out of this?

Last edited by thethinker; 05-13-2018 at 05:51 PM.
 
Old 05-13-2018, 05:51 PM   #2
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,231
Blog Entries: 4

Rep: Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747Reputation: 1747
Hi, your installation is 32 bit [1]. You shouldn't have installed multilib and now your system is very broken

Multilib is a way of adding 32 bit support into 64 bit Slackware. You didn't need multilib for 32 bit support because you already were pure 32 bit.

I'm not sure what the best way of fixing your system is going to be

[1] as proved by "Upgrading glibc-2.23-i586-4_slack14.2 package ..."
 
1 members found this post helpful.
Old 05-13-2018, 05:56 PM   #3
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,265

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
The OP probably wanted to add the x86_64 support to Slackware i586...

Last edited by Darth Vader; 05-13-2018 at 05:59 PM.
 
Old 05-13-2018, 06:57 PM   #4
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 167
Blog Entries: 2

Original Poster
Rep: Reputation: 28
Quote:
Originally Posted by 55020 View Post
Hi, your installation is 32 bit [1]. You shouldn't have installed multilib and now your system is very broken

Multilib is a way of adding 32 bit support into 64 bit Slackware. You didn't need multilib for 32 bit support because you already were pure 32 bit.

I'm not sure what the best way of fixing your system is going to be

[1] as proved by "Upgrading glibc-2.23-i586-4_slack14.2 package ..."
Wow ok....here's what happened.

I've been a Slack user for a while, but I just became a subscriber because you know, it's cool and I like it and whatever.

Got the DVD, flipped it over to the 64 bit side (see image)

Now, looking more closely, the side which is labeled 64 bit on the label is actually labeled 32 bit on the readout! (see attached pdf!)

So this is nuts, and I'm angry. Not that angry, but seriously....consistency! I just put this disk into another computer and sure enough, the *opposite* side is Slack 64. That is, for 64 bit you want BIG 32 bit label up, small 64 bit label up.

Was this my fault? Please say no.
Attached Files
File Type: pdf 32v64.pdf (358.5 KB, 58 views)
 
4 members found this post helpful.
Old 05-13-2018, 08:16 PM   #5
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,265

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
You are kidding, right?

Did you do not noticed the BOOT message yelling at you the operating system architecture?

For Slackware64, aka 64-bit, it is something like:
Quote:
Welcome to Slackware64 version 15.0 (Linux kernel 4.14.40)!
While for the Slackware 32-bit, aka i586, it will give you:
Quote:
Welcome to Slackware version 15.0 (Linux kernel 4.14.40)!
You have NO excuse.

Last edited by Darth Vader; 05-13-2018 at 09:49 PM.
 
2 members found this post helpful.
Old 05-13-2018, 10:13 PM   #6
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 167
Blog Entries: 2

Original Poster
Rep: Reputation: 28
Quote:
Originally Posted by Darth Vader View Post
You are kidding, right?

Did you do not noticed the BOOT message yelling at you the operating system architecture?

For Slackware64, aka 64-bit, it is something like:


While for the Slackware 32-bit, aka i586, it will give you:


You have NO excuse.
Now wait a second, that is not fair - in order to know "Slackware" refers to "32 bit Slackware" you have to know that the official name of "64 bit Slackware" is "Slackware64". Otherwise, why wouldn't I think the official name of the OS is the same for both versions? In most OS, this is true. Of course, I understand Slackware sets itself apart in this particular way, but if you don't remember that particular fact about this particular distro....?

Well, I know there is no love for nobblastism in Slack, so I'll just accept the grief and cry into my command line....
 
3 members found this post helpful.
Old 05-13-2018, 10:23 PM   #7
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,265

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Quote:
Originally Posted by thethinker View Post
Now wait a second, that is not fair - in order to know "Slackware" refers to "32 bit Slackware" you have to know that the official name of "64 bit Slackware" is "Slackware64".
It is more than fair, because if you do not know even the proper name of the operating system you are about to install, later you are literally a dead man.

As demonstrated by the complete mess you got in the final.

Please note that Slackware assumes that you are intelligent and informed man, not an "ubuntu" (be kind to look for the real sense of this word in Swahili language)

Last edited by Darth Vader; 05-13-2018 at 10:25 PM.
 
Old 05-13-2018, 10:43 PM   #8
vino29
LQ Newbie
 
Registered: Dec 2008
Location: in front of my PC
Distribution: Slackware
Posts: 6

Rep: Reputation: 8
@thethinker, i agree with you. the DVD you received was labeled wrongly. honest mistake from the DVD process and honest mistake on your part for installing Slackware 32 bit. we learn from our mistakes.

hopefully you are not put off by some of the members of this forum as the majority are very helpful.
 
6 members found this post helpful.
Old 05-13-2018, 11:35 PM   #9
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 296
Blog Entries: 2

Rep: Reputation: 123Reputation: 123
I don't have anything to add but I just wanted to try give some encouragement. I hope things look up from here.
 
1 members found this post helpful.
Old 05-14-2018, 03:41 AM   #10
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 686

Rep: Reputation: 215Reputation: 215Reputation: 215
Quote:
Originally Posted by thethinker View Post
So cd works, but that's kinda it. So I guess maybe the multilib packages from alienbob are not safe (although I strongly suspect I did something dumb...), but before I worry about that, does anyone have any idea how to get me out of this?
We've all been there, done that, in the "something dumb" department (I suspect even Darth Vader). I have a few humdingers my self, one heck of a learning experience for sure.

I have an idea, but I want to try it out first in a virtual machine. I don't have a Slackware-14.2 install iso so I have downloading one now. Going to follow what you did and see if I can fix it.

I am guessing that pkg-tools, slackpkg are broken right now.
 
1 members found this post helpful.
Old 05-14-2018, 05:50 AM   #11
GazL
Senior Member
 
Registered: May 2008
Posts: 4,683
Blog Entries: 12

Rep: Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180Reputation: 2180
This is why I don't like double-sided disks. Does the labeling on the face up side refer to what's on the face up side, or what's on the opposite side (and will be read by the drive). It's completely ambiguous. I have some dvd movie disks like that with 4x3 on one side and widescreen on the other and I'm always getting it wrong!
 
Old 05-14-2018, 08:14 AM   #12
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 821

Rep: Reputation: Disabled
darth, you can kindly take these musings of yours elsewhere
 
3 members found this post helpful.
Old 05-14-2018, 08:27 AM   #13
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 51

Rep: Reputation: 26
Excuse me, but it is hard to believe that someone will install Slackware in another architecture by mistake, then will configure and bring it up successfully without observing the wrong architecture, up to take the step to install multilib.

In my humble opinion, the OP just plays dumb, and what happened for real is just what Darth Vader said in his first post: the OP tried to add x86_64 support to a 32-bit Slackware.

Last edited by ZhaoLin1457; 05-14-2018 at 08:35 AM.
 
1 members found this post helpful.
Old 05-14-2018, 08:39 AM   #14
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,104

Rep: Reputation: Disabled
Quote:
Originally Posted by ZhaoLin1457 View Post
In my humble opinion, the OP just plays dumb, and what happened for real is just what Darth Vader said in his first post: the OP tried to add x86_64 support to a 32-bit Slackware.
Can you take your opinions elsewhere? Calling the OP a liar for a honest mistake is really low, just because Darth Vader is often rude doesn't mean you have to follow his poor example...
 
8 members found this post helpful.
Old 05-14-2018, 09:17 AM   #15
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,265

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Oh, now I am The Villain?

OK, let's play politically correct, and blame our BDFL that he made an installer so easy to use that even someone who have no clue what installs still manage to install Slackware, also let's blame Eric Hameleers that he do not specified clear that his multilib cannot add x86_64 support in a 32-bit system.

Also, let's propose to our BDFL to literally specify the architecture within boot screen, something like: "You are about to install the Slackware for 32-bit architercture!" and just to be sure, he should add a confirmation dialog on starting the installer, with the same sense.

Oh, and probably Eric should amend the docs and to specify clear that his multilib cannot add x86_64 support in a 32-bit system. Just in case.

Last edited by Darth Vader; 05-14-2018 at 09:21 AM.
 
1 members found this post helpful.
  


Reply


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] Would System Commands be Considered Those Commands under /bin? JockVSJock Linux - Newbie 2 04-26-2016 12:40 PM
multilib slackware64 <--I broke it, need advice smitchel1099 Slackware 17 11-20-2015 09:59 AM
Help! I think I broke the Less and Man commands... Biggen Linux - Newbie 3 09-30-2004 03:34 PM
adding commands to /bin (root user) xone Linux - Software 4 03-23-2004 12:26 PM
broke /bin/hostname nitsky416 Linux - Networking 2 11-30-2003 04:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:24 AM.

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