Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 4/7] enable _XOPEN_SOURCE on musl for wchar usage in curses
Date: Wed, 24 Aug 2022 11:44:10 +0200	[thread overview]
Message-ID: <20220824114410.4c9328aa@booty> (raw)
In-Reply-To: <20220824063443.1774094-4-raj.khem@gmail.com>

Hi Mhem,

On Tue, 23 Aug 2022 23:34:40 -0700
"Khem Raj" <raj.khem@gmail.com> wrote:

> This is defined for glibc automatically with _GNU_SOURCE but not for
> musl
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>

Missing 'pinentry: ' subject prefix. I added it when taking the patch
on my testing branch, no need to resend.

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-08-24  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  6:34 [PATCH 1/7] xinetd: Pass missing -D_GNU_SOURCE Khem Raj
2022-08-24  6:34 ` [PATCH 2/7] watchdog: Include needed system header for function decls Khem Raj
2022-08-24  6:34 ` [PATCH 3/7] libcgroup: Use GNU strerror_r only when its available Khem Raj
2022-08-24  6:34 ` [PATCH 4/7] enable _XOPEN_SOURCE on musl for wchar usage in curses Khem Raj
2022-08-24  9:44   ` Luca Ceresoli [this message]
2022-08-24 13:56     ` [OE-core] " Khem Raj
2022-08-24  6:34 ` [PATCH 5/7] apr: Use correct strerror_r implementation based on libc type Khem Raj
2022-08-24  6:34 ` [PATCH 6/7] gcr: Define _GNU_SOURCE Khem Raj
2022-08-24  6:34 ` [PATCH 7/7] ltp: Adjust types to match create_fifo_thread return Khem Raj

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=20220824114410.4c9328aa@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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