From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/pam: fix uclibc compile error
Date: Sat, 2 Sep 2023 17:51:02 +0200 [thread overview]
Message-ID: <20230902175102.3bbb46e2@windsurf> (raw)
In-Reply-To: <ZOsxD6Z372MejW1M@waldemar-brodkorb.de>
On Sun, 27 Aug 2023 13:18:39 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Following build failure occurs:
> opasswd.c: In function 'compare_password':
> opasswd.c:142:3: error: 'retval' undeclared (first use in this function); did you mean 'outval'?
> 142 | retval = outval != NULL && strcmp(outval, oldpass) == 0;
> | ^~~~~~
> | outval
>
> Add a patch from upstream to fix it.
> Happens since the update to 1.5.3 in Buildroot commit:
> f8147e27cdac8f998ec6644a09ce4e8d62b6433c
>
> Fixes:
> - http://autobuild.buildroot.net/results/576/576fc4b9ccbc6cff82569692bdec82192e89f036
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> ...Fix-build-if-crypt_r-isn-t-available.patch | 37 +++++++++++++++++++
> 1 file changed, 37 insertions(+)
> create mode 100644 package/linux-pam/0002-Fix-build-if-crypt_r-isn-t-available.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-02 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 11:18 [Buildroot] [PATCH] package/pam: fix uclibc compile error Waldemar Brodkorb
2023-09-02 15:51 ` Thomas Petazzoni via buildroot [this message]
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=20230902175102.3bbb46e2@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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