From: Bruno Thomsen <bth@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] sudo: version bump 1.8.22 -> 1.8.28
Date: Wed, 23 Oct 2019 08:56:39 +0000 [thread overview]
Message-ID: <HE1PR04MB3130772A2105E77772198ADBDC6B0@HE1PR04MB3130.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191015115823.3946-1-rhi@pengutronix.de>
Hi Roland
> Subject: [ptxdist] [PATCH] sudo: version bump 1.8.22 -> 1.8.28
>
> Pin down more configure options, and update the license MD5, which added
> some more file headers of files under ISC license, reformatted the
> existing license file headers, and bumped the copyright date to 2019.
Thanks for updating the rule.
After using this updated rule I hit a few runtime issues:
sudo --version
sudo: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory
sudo --version
sudo: error while loading shared libraries: libubsan.so.1: cannot open shared object file: No such file or directory
sudo --version
Sudo version 1.8.28
Below is a quick-and-dirty patch that fixes the issues.
I can send a proper patch if this is the correct way of fixing it as
it's most likely caused by a changed in the pinned configure options.
/Bruno
--------------------8<--------------------
diff --git a/rules/sudo.in b/rules/sudo.in
index 480c90cd9..aa47e4444 100644
--- a/rules/sudo.in
+++ b/rules/sudo.in
@@ -2,6 +2,8 @@
menuconfig SUDO
tristate
prompt "sudo "
+ select GCCLIBS_LIBASAN
+ select GCCLIBS_LIBUBSAN
select LIBC_CRYPT
select LIBC_UTIL
select LIBC_DL
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-10-23 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 11:58 Roland Hieber
2019-10-23 8:56 ` Bruno Thomsen [this message]
2019-10-23 9:05 ` Roland Hieber
2019-10-23 10:28 ` Michael Olbrich
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=HE1PR04MB3130772A2105E77772198ADBDC6B0@HE1PR04MB3130.eurprd04.prod.outlook.com \
--to=bth@kamstrup.com \
--cc=ptxdist@pengutronix.de \
--cc=rhi@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