Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] motion: fix build on musl
Date: Fri, 24 Nov 2017 09:38:26 +0100	[thread overview]
Message-ID: <20171124093826.021019e3@windsurf.lan> (raw)
In-Reply-To: <20171124063014.21029-1-fontaine.fabrice@gmail.com>

Hello,

On Fri, 24 Nov 2017 07:30:14 +0100, Fabrice Fontaine wrote:
> Some toolchains (musl) have pthread_setname_np but not pthread_getname_np.
> The first patch fixes check on pthread_setname_np and the second one add
> a check for pthread_getname_np
> 
> Fixes:
>  -
> http://autobuild.buildroot.net/results/65534775c5977e2424c5f5c63c46f9d0f39d7e1b
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  .../0001-Fix-pthread_setname_np-detection.patch    | 50 ++++++++++++++++
>  .../motion/0002-Check-for-pthread_getname_np.patch | 66 ++++++++++++++++++++++
>  2 files changed, 116 insertions(+)
>  create mode 100644 package/motion/0001-Fix-pthread_setname_np-detection.patch
>  create mode 100644 package/motion/0002-Check-for-pthread_getname_np.patch

Applied to next, thanks. Don't forget to send the patches upstream if
not already done. Thanks a lot for taking care of this build issue!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2017-11-24  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24  6:30 [Buildroot] [PATCH/next 1/1] motion: fix build on musl Fabrice Fontaine
2017-11-24  8:38 ` Thomas Petazzoni [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=20171124093826.021019e3@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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