On 04/20/16 07:40 PM, Michael Niedermayer wrote:
On Thu, Apr 14, 2016 at 07:31:48PM -0700, Dave Yeo wrote:
 From a417fdf752bd7c704ed5ba0c94c5cea96e1a91ff Mon Sep 17 00:00:00 2001
From: Dmitriy Kuminov <cod...@dmik.org>
Date: Thu, 14 Apr 2016 01:53:46 +0400
Subject: [PATCH 3/3] configure: Remove -Wredundant-decls on OS/2 to suppress
  noise.

This warning causes too much noise in libc 0.6.6- headers due to
duplicate function decls here and there.

Signed-off-by: Dave Yeo <daver...@telus.net>
---
  configure | 5 ++++-
  1 file changed, 4 insertions(+), 1 deletion(-)
[...]

maybe iam missing someting but
gcc doesnt/shouldnt report warnings for "system headers" AFAIK

[...]

It's strange. If I build under /usr/local/src with the standard environment (just tested with trunk), the warnings don't happen. When I built 3.0.1 in its own directory with the environment set up to find the libraries I'm linking against, eg $C_INCLUDE_PATH, $LIBRARY_PATH etc defined, I get warnings such as

CC      libavdevice/alldevices.o
In file included from K:/ffmpeg/src/ffmpeg-3.0.1/libavutil/common.h:36:0,
                 from K:/ffmpeg/src/ffmpeg-3.0.1/libavutil/avutil.h:288,
                 from K:/ffmpeg/src/ffmpeg-3.0.1/libavutil/log.h:25,
                 from K:/ffmpeg/src/ffmpeg-3.0.1/libavdevice/avdevice.h:46,
from K:/ffmpeg/src/ffmpeg-3.0.1/libavdevice/alldevices.c:22: K:/usr/include/math.h:495:17: warning: redundant redeclaration of 'nanl' [-Wredundant-decls]
 long double     nanl(const char *);
                 ^
K:/usr/include/math.h:466:13: note: previous declaration of 'nanl' was here
 long double nanl(const char *) __pure2;
             ^
K:/usr/include/math.h:530:13: warning: redundant redeclaration of 'log2l' [-Wredundant-decls]
 long double log2l(long double);
             ^
K:/usr/include/math.h:458:13: note: previous declaration of 'log2l' was here
 long double log2l(long double);
...

Not totally sure if suppressing all redundant declarations is the best option but it does quiet the noise.
I take it that Dmitriy is also building the RPMs in a separate environment.
Dave



_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to