[sword-devel] GCC warnings
Troy A. Griffitts
scribe at crosswire.org
Fri Dec 4 20:21:23 MST 2009
OK, glad we found that. I have a question though. There is a
significant performance gain for many features of SWORD when debugging
is turned off (which also turns -O3 on). When you build packages for
public consumption, don't you turn debugging off?
On Fri, 2009-12-04 at 13:05 -0800, Jonathan Marsden wrote:
> Matthew Talbert wrote:
> > Cross-compiled for Windows on Jaunty with gcc 4.4.2 with -Wall -Werror
> > and no problems (well, none related to those arguments).
> > Why would the build environment you set up be any different than stock Jaunty?
> Because debuild is apparently setting some compiler flags for us
> (somehow!). I'm still looking at the details.
> I can now get an svn (non-package) build to error out in the same way my
> package builds do, by making a one-character patch to configure.ac, as
> --- configure.ac (revision 2480)
> +++ configure.ac (working copy)
> @@ -90,7 +90,7 @@
> AM_CFLAGS="-O0 -Wall -Werror"
> if test x$ac_cv_prog_cxx_g = xyes; then
> - AM_CXXFLAGS="-g3 -O0 -Wall -Werror"
> + AM_CXXFLAGS="-g3 -O3 -Wall -Werror"
> AM_CXXFLAGS="-O0 -Wall -Werror"
> Having -O2 or higher enables the -D_FORTIFY_SOURCE=2 security hardening
> stuff, which is what is generating the warnings. The -Werror is then
> converting those to errors, and so halting the build process.
> See https://wiki.ubuntu.com/CompilerFlags for a bit more info about this
> What I don't yet know is how -O2 or higher is being enabled in my
> package builds...
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel