Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Sep 2004 17:50:26 GMT
From:      Giorgos Keramidas <keramida@freebsd.org>
To:        freebsd-doc@FreeBSD.org
Subject:   Re: docs/71359: /usr/share/examples/etc/make.conf contains broken CXXFLAGS
Message-ID:  <200409041750.i84HoQtx035444@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: Giorgos Keramidas <keramida@freebsd.org>
To: Chris Pepper <pepper@reppep.com>
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 20:47:44 +0300

 On 2004-09-04 11:31, Chris Pepper <pepper@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?
 



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