On Fri, Apr 03, 2009 at 01:47:00PM -0500, DRC wrote: > I would like to propose two changes to the CFLAGS in our build: > > (1) Adding a convenience option to the configure script that allows one > to pass an argument (for instance, 'configure --with-m32') that simply > adds -m32 to the default CFLAGS, CXXFLAGS, and LDFLAGS and sets the host > to i686-pc-linux-gnu. The problem with running > > ./configure --host i686-pc-linux-gnu --with-included-jpeg CFLAGS=-m32 > CXXFLAGS=-m32 LDFLAGS=-m32 > > is that it builds the code without optimization! One would really need to > run: > > ./configure --host i686-pc-linux-gnu --with-included-jpeg CFLAGS='-m32 -O3' > CXXFLAGS='-m32 -O3' LDFLAGS=-m32 > > and then similarly pass those arguments to build-xserver-7.4 to build Xvnc. > > I would prefer a solution that simply adds the -m32 flag rather than forcing > the user to specify all of the flags explicitly. > > > (2) I would like -O3 to be the default rather than -O2. This provides a bit > of additional performance for the Huffman codec. > > > The reason I'm mailing the list is that, after digging around and tinkering a > bit, I can't figure out how to implement either of the above. >
This doesn't look like proper approach for me. I think you should use shell script for such specific build. Question is if we want to use -O3 for libjpeg. Are you sure that we don't have any statement in jpeg code which is incompatible with -O3? If no and -O3 helps we should use it instead of O2. Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
