Jonathan, 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?
Troy 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 > follows: > > --- configure.ac (revision 2480) > +++ configure.ac (working copy) > @@ -90,7 +90,7 @@ > AM_CFLAGS="-O0 -Wall -Werror" > fi > if test x$ac_cv_prog_cxx_g = xyes; then > - AM_CXXFLAGS="-g3 -O0 -Wall -Werror" > + AM_CXXFLAGS="-g3 -O3 -Wall -Werror" > else > AM_CXXFLAGS="-O0 -Wall -Werror" > fi > > > 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 > topic. > > What I don't yet know is how -O2 or higher is being enabled in my > package builds... > > Jonathan > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
