[Re-sending from the right email address...] Good intuition. :) This is all I saw when compiling Chrome; looks like I misconfigured ffmpeg, though, so `make fate` was using GCC to compile things. With the correct configuration, I see a few more errors.
I'll send out v2 shortly. Thanks! On Tue, Aug 30, 2016 at 3:05 AM, Michael Niedermayer <mich...@niedermayer.cc > wrote: > On Tue, Aug 30, 2016 at 12:11:42AM -0700, George Burgess IV wrote: > > ChromeOS is adopting a new FORTIFY implementation tailored for clang. As > > an artifact of how this new FORTIFY is implemented, a handful of > > implicit conversion warnings get turned into errors. This patch fixes > > the implicit conversions in ffmpeg that clang-FORTIFY has an issue with. > > > > Signed-off-by: George Burgess IV <g...@chromium.org> > > --- > > libavutil/opt.c | 5 +++-- > > 1 file changed, 3 insertions(+), 2 deletions(-) > > does this patch fix the issue entirely or are there other patches > needed for other files ? > (asking as it seems odd that its just this) > > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Observe your enemies, for they first find out your faults. -- Antisthenes > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
