From: J.L. B. <jl...@ne...> - 2006-10-04 10:53:46
|
To continue my trials to work with opensync I obtained libopensync-0.19 (the latest) and tried to compile it (using rpmbuild). However, the use of the -Werror flag in the Makefile.am files results in the following errors: ________________________________________________ cc1: warnings being treated as errors opensync_wrap.c:214: warning: 'SWIG_TypeDynamicCast' defined but not used opensync_wrap.c:402: warning: 'SWIG_UnpackDataName' defined but not used opensync_wrap.c:482: warning: 'SWIG_PropagateClientData' defined but not used opensync_wrap.c:1181: warning: 'SWIG_Python_MustGetPtr' defined but not used opensync_wrap.c:1195: warning: 'SWIG_Python_ConvertPacked' defined but not used opensync_wrap.c:1479: warning: 'SWIG_Check_int' defined but not used opensync_wrap.c:3396: warning: 'SWIG_Python_addvarlink' defined but not used make[2]: *** [opensync_wrap.lo] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/libopensync-0.19/wrapper' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/libopensync-0.19' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.91433 (%build) ____________________________________________________________________ My question is why defining parameters when they are not used (in certain configurations). I also cannot see the use of the Werror flag in a rather stable product as in most cases warnings are just what they are: warnings. They don't produce an unstable run-time instance. In my case it prevents the compilation unnecessary. Is it possible to produce a version without the Werror activated? Joep |