Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adrian Bunk <bunk@stusta.de>, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V4 3/4] elfutils: Fix eu-* utils builds for musl
Date: Wed, 24 Jul 2019 09:24:13 +0100	[thread overview]
Message-ID: <531504ebcdae52b7ce1fe8221417d4026c0f9ceb.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190721152022.GA5474@localhost>

On Sun, 2019-07-21 at 18:20 +0300, Adrian Bunk wrote:
> On Sat, Jul 20, 2019 at 11:00:57AM -0700, Khem Raj wrote:
> > ...
> > ++#if !defined(FNM_EXTMATCH)
> > ++# define FNM_EXTMATCH (0)
> > ++#endif
> > ...
> 
> As already said in [1] this is expected to result in broken code,
> and the upstream testsuite also confirms this.

I've taken the patches as they don't make things worse. I am a bit
concerned about a few places musl is building up problematic patches
though (systemd, elfutils, ltp come to mind).

Cheers,

Richard



  reply	other threads:[~2019-07-24  8:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20 18:00 [PATCH V4 1/4] pam_systemd: Include missing.h for secure_getenv Khem Raj
2019-07-20 18:00 ` [PATCH V4 2/4] musl-obstack: Add recipe Khem Raj
2019-07-20 18:00 ` [PATCH V4 3/4] elfutils: Fix eu-* utils builds for musl Khem Raj
2019-07-21 15:20   ` Adrian Bunk
2019-07-24  8:24     ` Richard Purdie [this message]
2019-07-24 13:39       ` Khem Raj
2019-07-24 14:58         ` Adrian Bunk
2019-07-24 17:39           ` Khem Raj
2019-07-20 18:00 ` [PATCH V4 4/4] maintainers: Account for musl-obstack and libssp-nonshared 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=531504ebcdae52b7ce1fe8221417d4026c0f9ceb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bunk@stusta.de \
    --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