From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Anisse Astier <anisse@astier.eu>,
Thomas Perale <thomas.perale@mind.be>,
Christian Stewart <christian@aperture.us>,
Thomas Perale <thomas.perale@essensium.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/ffmpeg: fix build error
Date: Sat, 14 Sep 2024 21:56:03 +0200 [thread overview]
Message-ID: <20240914215603.17de98b6@windsurf> (raw)
In-Reply-To: <20240914183850.273831-1-thomas.perale@mind.be>
On Sat, 14 Sep 2024 20:38:50 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
> ffmpeg builds with `--enable-vaapi` opt made GCC v14 and 32 bit target
> will throw an 'Wincompatible-pointer-types' error.
>
> This is a downport of an upstreamed commit but not yet present in any
> ffmpeg version that fix the pointer type.
>
> Fixes:
> - http://autobuild.buildroot.org/results/f5f/f5f2d16226ad9500ecf046779d5282ee071a54d3/
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
> ...hwcontext-vaapi-use-the-correct-type.patch | 28 +++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 package/ffmpeg/0007-avutil-hwcontext-vaapi-use-the-correct-type.patch
Applied to master, thanks.
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
next prev parent reply other threads:[~2024-09-14 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 18:38 [Buildroot] [PATCH 1/1] package/ffmpeg: fix build error Thomas Perale via buildroot
2024-09-14 19:56 ` Thomas Petazzoni via buildroot [this message]
2024-10-11 12:52 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2024-09-14 15:36 Thomas Perale via buildroot
2024-09-14 16:23 ` Thomas Petazzoni via buildroot
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=20240914215603.17de98b6@windsurf \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=christian@aperture.us \
--cc=thomas.perale@essensium.com \
--cc=thomas.perale@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.