public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: mgorman@suse.de, jack@suse.cz, vbabka@suse.cz, dave@stgolabs.net,
	ziy@nvidia.com, yuzhao@google.com, jhubbard@nvidia.com,
	ryan.roberts@arm.com
Cc: kdevops@lists.linux.dev, cl@os.amperecomputing.com,
	yang@os.amperecomputing.com, p.raghav@samsung.com,
	da.gomez@samsung.com, gost.dev@samsung.com,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: [mmtests PATCH v4 1/2] bin/install-depends: call ldconfig
Date: Tue, 18 Jun 2024 11:11:57 -0700	[thread overview]
Message-ID: <20240618181158.3848619-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20240618181158.3848619-1-mcgrof@kernel.org>

Some packages may have bugs and forgot to run ldconfig, work around
these bugs by ensuring we call ldconfig after installation *all*
required packages, we do this just once for a set of packages.

Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 bin/install-depends | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/bin/install-depends b/bin/install-depends
index e0052f274027..a7cfaa49977b 100755
--- a/bin/install-depends
+++ b/bin/install-depends
@@ -254,6 +254,11 @@ foreach my $package (@ARGV) {
 	print "Installed $package\n";
 }
 
+if (system("ldconfig") != 0) {
+	print "ERROR: ldconfig failed\n";
+	exit(-1);
+}
+
 if ($ENV{"MMTESTS_SESSION_ID"} ne "") {
 	close(SESSION);
 }
-- 
2.43.0


  reply	other threads:[~2024-06-18 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 18:11 [mmtests PATCH v4 0/2] mmtests: fix debian dependencies Luis Chamberlain
2024-06-18 18:11 ` Luis Chamberlain [this message]
2024-06-18 18:11 ` [mmtests PATCH v4 2/2] MMTests::Stat: replace List::BinarySearch Luis Chamberlain
2024-06-22 10:38 ` [mmtests PATCH v4 0/2] mmtests: fix debian dependencies Mel Gorman

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=20240618181158.3848619-2-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cl@os.amperecomputing.com \
    --cc=da.gomez@samsung.com \
    --cc=dave@stgolabs.net \
    --cc=gost.dev@samsung.com \
    --cc=jack@suse.cz \
    --cc=jhubbard@nvidia.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mgorman@suse.de \
    --cc=p.raghav@samsung.com \
    --cc=ryan.roberts@arm.com \
    --cc=vbabka@suse.cz \
    --cc=yang@os.amperecomputing.com \
    --cc=yuzhao@google.com \
    --cc=ziy@nvidia.com \
    /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