Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Sep 2004 16:30:22 GMT
From:      Chris Pepper <pepper@reppep.com>
To:        freebsd-doc@FreeBSD.org
Subject:    Re: docs/71359: /usr/share/examples/etc/make.conf contains broken CXXFLAGS
Message-ID:  <200409041630.i84GUMXt027498@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/71359; it has been noted by GNATS.

From: Chris Pepper <pepper@reppep.com>
To: Giorgos Keramidas <keramida@freebsd.org>
Cc: Paul Mather <paul@gromit.dlib.vt.edu>, bug-followup@freebsd.org
Subject: Re: docs/71359: /usr/share/examples/etc/make.conf contains broken
 CXXFLAGS
Date: Sat, 4 Sep 2004 11:31:51 -0400

 At 3:46 PM +0300 2004/09/04, Giorgos Keramidas wrote:
 >On 2004-09-03 23:31, Chris Pepper <pepper@reppep.com> wrote:
 >>  >Description:
 >  >	/usr/share/examples/etc/make.conf suggests:
 >>  CXXFLAGS+= -fmemoize-lookups -fsave-memoized
 >>	but this prevents make buildworld in RELENG_5.
 >>  [...]
 >>  >Fix:
 >>  Remove this sample from the example, or replace it with one that's
 >>  safe under RELENG_5
 >
 >You don't *have* to use the same CXXFLAGS options as the ones of the
 >example.  It's an example, after all.  Anyway, would you prefer something
 >like this instead?
 
 	Of course, but the examples should all be valid. This one 
 prevents make buildworld, so should be replaced by something that 
 doesn't.
 
 >     # CXXFLAGS controls the compiler settings used when compiling C++ code.
 >     # Note that CXXFLAGS is initially set to the value of CFLAGS.  If you wish
 >     # to add to CXXFLAGS value, "+=" must be used rather than "=".  Using "="
 >     # alone will remove the often needed contents of CFLAGS from CXXFLAGS.
 >    +# For a description of the options recognized by the GNU C++ compiler
 >    +# please refer to the c++(1) manpage and the info documentation of GCC.
 >     #
 >    -#CXXFLAGS+= -fmemoize-lookups -fsave-memoized
 >    +#CXXFLAGS+= -O -pipe
 
 	Except that's provided already with the example of CFLAGS, so 
 would make sense iff CFLAGS had another example value.
 
 # CFLAGS controls the compiler settings used when compiling C code.
 # Note that optimization settings other than -O and -O2 are not recommended
 # or supported for compiling the world or the kernel - please revert any
 # nonstandard optimization settings to "-O" before submitting bug reports
 # without patches to the developers.
 # Note also that at this time the -O2 setting is known to expose bugs in
 # libalias(3), and possibly other parts of the system.
 #
 #CFLAGS= -O -pipe
 #
 # CXXFLAGS controls the compiler settings used when compiling C++ code.
 # Note that CXXFLAGS is initially set to the value of CFLAGS.  If you wish
 # to add to CXXFLAGS value, "+=" must be used rather than "=".  Using "="
 # alone will remove the often needed contents of CFLAGS from CXXFLAGS.
 #
 #CXXFLAGS+= -fmemoize-lookups -fsave-memoized
 
 
 						Regards,
 
 
 						Chris Pepper
 --
 Chris Pepper:               <http://www.reppep.com/~pepper/>;
 Rockefeller University:     <http://www.rockefeller.edu/>;



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409041630.i84GUMXt027498>