Oliver Stöneberg wrote:
> Sorry...overlooked that.
>
> Yes, it is a custom build system, but what does have to do with the
> code causing a warning with GCC/clang, that is enabled by default?
I don't know, its your build system and I haven't seen it, nor do
I have the time and motivation to look at it (unless of course you
were paying me for my time). I willing give my time to maintain
FLAC. I have not signed up to spend my time on your project.
> Unless you disable this warning in your build system.
Well, you can look at our build system for yourself, but I can assure
you that when I'm compiling FLAC in development (ie configured using
"./configure --enable-werror") I am compiling with:
-Wall -Wextra -Wstrict-prototypes -Wmissing-prototypes
-Waggregate-return -Wcast-align -Wnested-externs -Wshadow -Wundef
-Wmissing-declarations -Wunreachable-code -Winline
-Wdeclaration-after-statement -Werror
> Just using
> autoconf or cmake instead of gcc/clang directly doesn't make them
> compiler behave differently - unless you tell them to ;)
Our autotool build system generates at least one header file (config.h,
in the top level directory). Unless your build system generates the
exact same header file, the results will be different.
Our build system does not deisplay that warning (as you can easily
prove for yourself, hint trying building with "V=1 make" so see the
full compiler invocation). That should be the end of this discussion.
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
_______________________________________________
flac-dev mailing list
flac-dev@xiph.org
http://lists.xiph.org/mailman/listinfo/flac-dev
