Date: Thu, 29 Nov 2012 19:15:23 -0500 From: Eitan Adler <eadler@freebsd.org> To: Bruce Evans <brde@optusnet.com.au> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r243670 - head/share/man/man5 Message-ID: <CAF6rxgkUVrWbOU2i2=16St1iyWJskeULpWjDT5hEZi0aX%2BsHCQ@mail.gmail.com> In-Reply-To: <20121130110154.E1441@besplex.bde.org> References: <201211291251.qATCpA7w078277@svn.freebsd.org> <20121130110154.E1441@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 November 2012 19:09, Bruce Evans <brde@optusnet.com.au> wrote: > On Thu, 29 Nov 2012, Eitan Adler wrote: > "gcc" was mostly correct here, since the flags are unportable gcc ones. > They don't work with any "cc", but may work with clang, although this > is unclear since none of them is documented in clang(1). Every time I talk to the clang folk about flags they point me to gcc documentation. > However, I never would have agreed to putting any of them here. > > Lots here is now superseded by flags set by WARNS anyway. > > clang's even more unportable new flags are not documented in clang(1) > and the settings here are too old to have dreamed of these. The reference to BDECFLAGS actually isn't true - there is no such variable. There is a *commented out* version which I had planned to email you about at some point. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkUVrWbOU2i2=16St1iyWJskeULpWjDT5hEZi0aX%2BsHCQ>