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 v3] vlc: fix compile error with uClibc-ng Linuxthreads
Date: Sat, 27 Aug 2016 14:47:06 +0200	[thread overview]
Message-ID: <20160827144706.6df2379a@free-electrons.com> (raw)
In-Reply-To: <20160826212727.GA21169@waldemar-brodkorb.de>

Hello,

On Fri, 26 Aug 2016 23:27:27 +0200, Waldemar Brodkorb wrote:
> The fallback code path didn't work correctly, so fix it.
> 
> Fixes:
>   http://autobuild.buildroot.net/results/3122287ddea1e316a64ccf0d0dc9415bfefebb49/
> 
> Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v2 -> v3:
>  - use git format patch, requested by Thomas Petazzoni
>  - remove unneeded -lpthread, requested by Thomas Petazzoni
> v1 -> v2:
>  - rework autobuild failure, there is fallback code for non-NPTL,
>    so fix it up. Suggested by Thomas Petazzoni
> ---
>  ...ck-code-and-add-required-realtime-library.patch | 40 ++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
>  create mode 100644 package/vlc/0008-fix-fallback-code-and-add-required-realtime-library.patch

I've applied to master. But in fact, the change in VLC should have made
using two separate patches, as they are not directly related.

Could you please split them in two patches, and submit them upstream?
Once it gets accepted upstream, we can backport the final version.

Thanks a lot!

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

      reply	other threads:[~2016-08-27 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 21:27 [Buildroot] [PATCH v3] vlc: fix compile error with uClibc-ng Linuxthreads Waldemar Brodkorb
2016-08-27 12:47 ` 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=20160827144706.6df2379a@free-electrons.com \
    --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