Troy A. Griffitts wrote:
> 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?
I simply
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:
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 fo
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?
Matthew
___
sword-devel mailing list: sword-d
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include
> -I/usr/include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__
> -DSWICU_DATA=\"/usr/lib/sword/1.6.0_icu_4.0.1\" -D_FTPLIB_NO_COMPAT
> -D_ICU_ -g3 -O0 -Wall -Werror -D_ICU_ -ftemplate-depth-25
> -DCURLAVAILABLE -I/usr/include -I/
Deji Akingunola wrote:
>> g++ | 4:4.3.3-1ubuntu1 |jaunty | amd64, i386
>> g++ | 4:4.4.1-1ubuntu2 |karmic | amd64, i386
> Those are actually 4.3.3 and 4.4.1 which are older than Fedora's
> 4.4.2. There is no gcc-4.4.3 yet.
Thanks. I somehow read the colons as periods.
