Github messages for voidlinux
 help / color / mirror / Atom feed
From: twpayne <twpayne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ldd is broken in default install (missing dependency on bash)
Date: Mon, 29 Nov 2021 23:14:52 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34319@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

New issue by twpayne on void-packages repository

https://github.com/void-linux/void-packages/issues/34319

Description:
### System

* xuname:  
  `Void 5.4.0-86-generic x86_64 GenuineIntel uptodate rF`
* package:  
  *affected package(s) including the version*: Sorry, I could not find out which package provides `/usr/sbin/ldd`.

### Expected behavior

`ldd --version` prints a version number and copyright notice.

### Actual behavior

`ldd --version` fails with the error:

```
/bin/sh: 1: ldd: not found
```

### Steps to reproduce the behavior

With Docker:

```console
$ docker run -it voidlinux/voidlinux:latest /bin/sh
# ldd
/bin/sh: 1: ldd: not found
```

### Explanation

`/usr/sbin/ldd` is a bash script:
```console
$ head -n 1 /usr/sbin/ldd
#!/bin/bash
```
By default, `bash` is not installed, so `/usr/sbin/ldd` fails with the "not found" error shown above.

### Possible fixes

1. Install `/bin/bash` as part of the base system.
2. Modify `/usr/sbin/ldd` to use `/bin/sh` instead of `/bin/bash`, as `/bin/sh` is part of the base system.

Please let me know if you need any further information.

             reply	other threads:[~2021-11-29 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 22:14 twpayne [this message]
2021-11-29 22:45 ` ericonr
2021-11-29 22:46 ` ericonr
2021-11-29 22:56 ` ericonr
2021-11-29 22:57 ` ericonr
2021-11-30 12:10 ` twpayne
2021-12-02  0:13 ` [ISSUE] [CLOSED] " ericonr
2022-02-19  3:35 ` illiliti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34319@inbox.vuxu.org \
    --to=twpayne@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).