(SOLVED) moved c library file bash stopped recognizing commands

Forum Forums News Sid Upgraders (SOLVED) moved c library file bash stopped recognizing commands

  • This topic has 8 replies, 4 voices, and was last updated Mar 26-6:00 pm by stevesr0.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #33823
    Member
    stevesr0

      After an interval of several days, I rebooted my sid install and performed a update and full-upgrade.

      Error indicating that the C library file ld-2.30.so was blocking an update because it was in a specific directory /usr/lib/x86_64-linux-gnu.

      It “suggested” removing the file from that directory.

      I did that (mv’ing it to my home directory and thereafter, bash no longer “finds” commands (sudo, ls, mv, copy).

      I checked the path and noted it was missing references to /usr/local/sbin (and maybe some others).

      So I modified it to /usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/usr/bin:/bin:/sbin:/usr/local/games:/usr/games:/home/stevesr0.

      Unfortunately, this hasn’t changed the failure of bash to find the commands!

      Thankfully, I am using this install as a learning experience, so if necessary, I can just perform a new install.

      BUT as a learning experience, I would like to understand how moving this C library file caused this damage (and ideally how to fix it). And how to install the update that refused to be installed until the file was moved.

      Addendum: Just looked up the LD_LIBRARY_PATH setting – maybe just setting that to my home directory would work? I will wait for feedback, because I don’t need to rush and that might upset other C library file functions that AREN’T in my home directory.

      Thanks in advance.

      stevesr0

      • This topic was modified 3 years, 1 month ago by stevesr0.
      • This topic was modified 3 years, 1 month ago by stevesr0.
      • This topic was modified 3 years, 1 month ago by stevesr0.
      #33837
      Member
      fungalnet
        Helpful
        Up
        0
        ::

        I’d say put the lib back where it was and reupdate or change mirrors. It may be a partial mirroring problem that created the conflict of upgrades. There is an ongoing shift from gcc8 to gcc9 but I didn’t experience the conflict in my sid(s) just this past hour.

        #33838
        Member
        fatmac
          Helpful
          Up
          0
          ::

          Put it back where it belongs would be my suggestion too. 🙂

          Probably a glitch in version numbering on the update/upgrade, I’d just wait a day or so, then try again.

          Linux (& BSD) since 1999

          #33853
          Member
          stevesr0
            Helpful
            Up
            0
            ::

            To fungalnet and fatmac,

            Yes, that was the first thing I tried.

            Using commands that bash no longer recognized (-bash: mv no such file or directory…).

            That is my question – how to I get bash to recognize the commands to move the file back where it belongs!

            I think bash requires that C library to be able to find/use the commands.

            bash apparently doesn’t know where to look for the C library, except in the expected directory.

            That is why I asked about using the LD_LIBRARY_PATH to tell it where to look.

            BUT, I am ignorant about the need for other C library files still in the original directory if I do that.
            I once used the PRELOAD version of this command to enable a particular application to work but it was a long, long, long time ago and I am scared when it comes to messing with the C library files (not really scared – I would like to learn how to do this properly).

            I know, from looking online last night, that others have used the LD_LIBRARY_PATH command to tell a script where to find the necessary library file, but I haven’t found a site to explain it to noobies, yet.)

            OH, finally the other reason for posting was to see if anyone else had a similar problem arise with updating that C library file.

            Thanks for responses, d I will repost if I get it figured out.

            stevesr0

            #33854
            Forum Admin
            anticapitalista
              Helpful
              Up
              0
              ::

              Why not open 2 instances of rox file manager as root and drag the lib to where it was.

              Philosophers have interpreted the world in many ways; the point is to change it.

              antiX with runit - leaner and meaner.

              #33859
              Member
              stevesr0
                Helpful
                Up
                0
                ::

                Hi anticapitalista,

                I am running a command line only install. I don’t think rox is installed.

                I figure that only “built in” commands will work, like PATH (it does) and LD_LIBRARY_PATH (haven’t tried yet, because I don’t know if that might make other C library inoperative.

                Perhaps this question is better posted/moved to the software or general questions forum?

                Thanks for response.

                stevesr0

                • This reply was modified 3 years, 1 month ago by stevesr0.
                #33863
                Forum Admin
                anticapitalista
                  Helpful
                  Up
                  0
                  ::

                  You could use a command line installer such as mc.

                  Or boot antiX-base live usb and use rox to make the change.
                  Your installed version of antiX should show up under /media.

                  • This reply was modified 3 years, 1 month ago by anticapitalista.

                  Philosophers have interpreted the world in many ways; the point is to change it.

                  antiX with runit - leaner and meaner.

                  #33866
                  Member
                  stevesr0
                    Helpful
                    Up
                    0
                    ::

                    Hi anticapitalista,

                    Nothing works from the command line that depends upon bash.

                    I tried launching mc (/usr/bin/mc) and get the usual message – “-bash no such file”.

                    Bash, it seems, is REALLY messed up.

                    I will try running the liveusb and moving that file back where it belongs.

                    BTW, any idea why the upgrade or update of that file was impossible when that prior file was in the right directory?

                    Thanks.

                    stevesr0
                    P.S. stay well.

                    #33870
                    Member
                    stevesr0
                      Helpful
                      Up
                      0
                      ::

                      UPDATE: Gave up with trying to fix it from within and following anticapitalista’s suggestion, launched a liveusb and moved the file back (had to unlink a symbolic link first).

                      Amazingly, it seems to be as good as new!

                      Thanks

                      stevesr0.

                    Viewing 9 posts - 1 through 9 (of 9 total)
                    • You must be logged in to reply to this topic.