From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][kirkstone 16/16] libxcrypt: fixed some build error for nativesdk with mingw
Date: Thu, 23 Nov 2023 12:39:10 +0000 [thread overview]
Message-ID: <c54ab4f4e673b355bb0ee37bbf2d33c6dc0565fb.camel@linuxfoundation.org> (raw)
In-Reply-To: <ca4866d14f725ae6c99c6651a69333d9453713a2.1700620126.git.steve@sakoman.com>
On Tue, 2023-11-21 at 16:31 -1000, Steve Sakoman wrote:
> From: Wenlin Kang <wenlin.kang@windriver.com>
>
> Steps to reproduce
> 1) add layer meta-mingw
> 2) add line in local.conf
> SDKMACHINE = "x86_64-mingw32"
> 3) bitbake nativesdk-libxcrypt
>
> Fixed:
> 1. .symver error
> | {standard input}: Assembler messages:
> | {standard input}:4: Error: unknown pseudo-op: `.symver'
>
> 2. pedantic error
> | ../git/lib/crypt.c:316:24: error: ISO C does not allow extra ';' outside of a function [-Werror=pedantic]
> | 316 | SYMVER_crypt_gensalt_rn;
> | |
>
> 3. conversion error
> | ../git/lib/util-get-random-bytes.c: In function '_crypt_get_random_bytes':
> | ../git/lib/util-get-random-bytes.c:140:42: error: conversion from 'size_t' {aka 'long long unsigned int'} to 'unsigned int' may change value [-Werror=conversion]
> | 140 | ssize_t nread = read (fd, buf, buflen);
>
> Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
> .../0001-Fix-for-compilation-on-Windows.patch | 37 +++++++++++++++
> ...dom-bytes.c-fixed-conversion-error-w.patch | 47 +++++++++++++++++++
> meta/recipes-core/libxcrypt/libxcrypt.inc | 4 ++
> 3 files changed, 88 insertions(+)
> create mode 100644 meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch
> create mode 100644 meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch
This isn't in master, not is it going to be.
Cheers,
Richard
next prev parent reply other threads:[~2023-11-23 12:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 2:30 [OE-core][kirkstone 00/16] Patch review Steve Sakoman
2023-11-22 2:30 ` [OE-core][kirkstone 01/16] tiff: Backport fix for CVE-2023-41175 Steve Sakoman
2023-11-22 2:30 ` [OE-core][kirkstone 02/16] grub: fix CVE-2023-4692 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 03/16] qemu 6.2.0: Fix CVE-2023-1544 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 04/16] avahi: fix CVE-2023-38471 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 05/16] avahi: fix CVE-2023-38470 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 06/16] avahi: fix CVE-2023-38469 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 07/16] avahi: fix CVE-2023-38472 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 08/16] avahi: fix CVE-2023-38473 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 09/16] binutils: Fix CVE-2022-47007 Steve Sakoman
2023-11-23 12:41 ` Richard Purdie
2023-11-23 14:49 ` Steve Sakoman
2023-11-23 14:54 ` Richard Purdie
2023-11-22 2:31 ` [OE-core][kirkstone 10/16] binutils: Fix CVE-2022-48064 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 11/16] ghostscript: ignore GhostPCL CVE-2023-38560 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 12/16] go: ignore CVE-2023-45283 and CVE-2023-45284 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 13/16] sudo: upgrade 1.9.13p3 -> 1.9.15p2 Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 14/16] go: Fix issue in DNS resolver Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 15/16] goarch: Move Go architecture mapping to a library Steve Sakoman
2023-11-23 12:40 ` Richard Purdie
2023-11-23 13:45 ` Bruce Ashfield
2023-11-23 14:53 ` Steve Sakoman
2023-11-22 2:31 ` [OE-core][kirkstone 16/16] libxcrypt: fixed some build error for nativesdk with mingw Steve Sakoman
2023-11-23 12:39 ` Richard Purdie [this message]
2023-11-23 14:37 ` Steve Sakoman
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=c54ab4f4e673b355bb0ee37bbf2d33c6dc0565fb.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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