Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ffmpeg: handle new SDL2 version scheme
Date: Fri, 28 Oct 2022 12:03:12 +0200	[thread overview]
Message-ID: <20221028120312.4e1479ab@windsurf> (raw)
In-Reply-To: <20221016080629.3354482-1-clabbe@baylibre.com>

On Sun, 16 Oct 2022 08:06:29 +0000
Corentin Labbe <clabbe@baylibre.com> wrote:

> Current ffmpeg package does not install ffplay.
> The root cause is that ffmpeg configure does not detect SDL2 due to
> version mismatch.
> The patch fixing that is taken from gentoo portage tree.
> 
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> ---
>  ...peg-4.4.2-libsdl2-new-version-scheme.patch | 25 +++++++++++++++++++
>  1 file changed, 25 insertions(+)
>  create mode 100644 package/ffmpeg/0005-ffmpeg-4.4.2-libsdl2-new-version-scheme.patch

Thanks Corentin for the patch. However on the same day, Bernd submitted
a patch that bumps ffmpeg to 4.4.3, which also addresses the problem as
this fix is already in ffmpeg 4.4.3.

Also, for next contributions: we want the patch to be generated with
"git format-patch", and you need to add your Signed-off-by line in the
patch itself.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-10-28 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  8:06 [Buildroot] [PATCH] package/ffmpeg: handle new SDL2 version scheme Corentin Labbe
2022-10-16 10:43 ` Joachim Wiberg
2022-10-28 10:03 ` Thomas Petazzoni via buildroot [this message]
     [not found] <20221016080629.3354482-1-clabbe__38958.9544081659$1665907620$gmane$org@baylibre.com>
2022-10-16 15:21 ` Bernd Kuhls

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=20221028120312.4e1479ab@windsurf \
    --to=buildroot@buildroot.org \
    --cc=clabbe@baylibre.com \
    --cc=thomas.petazzoni@bootlin.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