mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] monit: Add dependency to nsl
Date: Mon, 24 Oct 2022 10:30:35 +0200	[thread overview]
Message-ID: <20221024083035.32746-1-ada@thorsis.com> (raw)

Console log is flooded with this:

    /usr/bin/monit: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

Output of readelf is this:

    Dynamic section at offset 0xa5a50 contains 35 entries:
      Tag        Type                         Name/Value
     0x00000001 (NEEDED)                     Shared library: [librt.so.1]
     0x00000001 (NEEDED)                     Shared library: [libm.so.6]
     0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
     0x00000001 (NEEDED)                     Shared library: [libcrypt.so.1]
     0x00000001 (NEEDED)                     Shared library: [libresolv.so.2]
     0x00000001 (NEEDED)                     Shared library: [libnsl.so.1]
     0x00000001 (NEEDED)                     Shared library: [libc.so.6]
     0x00000001 (NEEDED)                     Shared library: [ld-linux-armhf.so.3]

Console log flooding is gone after setting the option.

Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
 rules/monit.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/rules/monit.in b/rules/monit.in
index 383433e78..9db337331 100644
--- a/rules/monit.in
+++ b/rules/monit.in
@@ -3,6 +3,7 @@
 menuconfig MONIT
 	tristate
 	prompt "monit                         "
+	select LIBC_NSL
 	select OPENSSL if MONIT_SSL
 	select ZLIB if MONIT_ZLIB
 	select BUSYBOX_START_STOP_DAEMON if MONIT_STARTSCRIPT

base-commit: 30caaac3f949cf650402516f80807d22af46bd4e
-- 
2.30.2




             reply	other threads:[~2022-10-24  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  8:30 Alexander Dahl [this message]
2022-10-24 12:28 ` Alexander Dahl
2022-10-24 13:01   ` Alexander Dahl
2022-11-18 11:32     ` Michael Olbrich
2022-11-21 14:29       ` Alexander Dahl

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=20221024083035.32746-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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