GCC_OPTIONS
David O'Brien
obrien at FreeBSD.org
Fri Apr 4 09:52:12 PST 2003
On Fri, Apr 04, 2003 at 08:26:52PM +0300, Ruslan Ermilov wrote:
> On Fri, Apr 04, 2003 at 08:30:13AM -0800, David O'Brien wrote:
> > On Fri, Apr 04, 2003 at 11:07:46AM +0300, Ruslan Ermilov wrote:
> > > Guess what was in GCC_OPTIONS. In short, we don't support
> > > GCC_OPTIONS. It isn't even mentioned in gcc(1) or GNU info
> > > files.
> >
> > We, FreeBSD, are the ones that added it. That's why it isn't mentioned
> > in the GNU docs.
> >
> : revision 1.20
> : date: 2001/05/29 09:54:45; author: obrien; state: Exp; lines: +53 -1
> : Support the environmental var "GCC_OPTIONS". Which can hold a set of
> : default options for GCC. These options are interpreted first and can be
> : overwritten by explicit command line parameters. This provides one way of
> : adding [temporary] options to your world build w/o editing /etc/make.conf.
>
> So this is only to add temporary options to the default CFLAGS,
> where simple
>
> make CFLAGS="`make -V CFLAGS` -foo -bar"
>
> would do just fine? Are there any other reasons behind adding
> this variable?
Say I always want -g, or -save-temps, or any of several other options.
It is easier to add GCC_OPTIONS to ~/.<shell> than always type it on the
command line. We also have DIFF_OPTIONS, GREP_OPTIONS. I guess you
don't need to take it into account, but should a weird bug report crop
up, it is something to keep in mind.
More information about the cvs-src
mailing list