Hello, The libipoddevice ebuild compiles with -Werror flag, causing the warnings to be treated as errors. And there is a warning. [code]i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -Wall -Werror -ggdb3 -D_FORTIFY_SOURCE=2 -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/hal -I/usr/include/libgtop-2.0 -I/usr/include/libxml2 -O3 -march=prescott -pipe -falign-functions=4 -fprefetch-loop-arrays -fomit-frame-pointer -MT glib-compat.lo -MD -MP -MF .deps/glib-compat.Tpo -c glib-compat.c -o glib-compat.o >/dev/null 2>&1 cc1: warnings being treated as errors hal-ipod-info.c: In function
Hello, The libipoddevice ebuild compiles with -Werror flag, causing the warnings to be treated as errors. And there is a warning. [code]i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -Wall -Werror -ggdb3 -D_FORTIFY_SOURCE=2 -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/hal -I/usr/include/libgtop-2.0 -I/usr/include/libxml2 -O3 -march=prescott -pipe -falign-functions=4 -fprefetch-loop-arrays -fomit-frame-pointer -MT glib-compat.lo -MD -MP -MF .deps/glib-compat.Tpo -c glib-compat.c -o glib-compat.o >/dev/null 2>&1 cc1: warnings being treated as errors hal-ipod-info.c: In function hal_ipod_write_xml: hal-ipod-info.c:137: attention : ignoring return value of asprintf, declared with attribute warn_unused_result[/code] -Werror flags must therefore be removed from src/Makefile.[in|am].
Yes it's normal, you shouldn't ever use -Werror CFLAG it only causes troubles. And all this are just warnings it doesn't mean it's wrong (errors) so there's no point to add -Werror to CFLAGS or build a patch to fix this. The upstream know when it should use -Werror or not.
