docs/71359: /usr/share/examples/etc/make.conf contains broken CXXFLAGS

[Chris Pepper]

The following reply was made to PR docs/71359; it has been noted by GNATS.

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

 At 8:47 PM +0300 2004/09/04, Giorgos Keramidas wrote:
 >On 2004-09-04 11:31, Chris Pepper <pepper at reppep.com> wrote:
 >>
 >>	Of course, but the examples should all be valid. This one
 >>  prevents make buildworld, so should be replaced by something that
 >>  doesn't.
 >
 >True, true.
 >
 >>  >    # 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.
 >
 >I don't use C++ so much, so perhaps I'm not the right person to choose a
 >"nice set of default flags" for this.
 >
 >Any ideas from you, Chris?
 
 	No idea, sorry. If we don't have (get) one, it should 
 probably be left blank (e.g., "#CXXFLAGS+="), and the explanation 
 will have to serve.
 
 	That would still be a substantial improvement over the 
 current state of affairs.
 
 
 						Chris Pepper
 -- 
 Chris Pepper:               <http://www.reppep.com/~pepper/>
 Rockefeller University:     <http://www.rockefeller.edu/>