Re: groff and mkdep?

I wasn't running make with -e.
I believe the commandline was similar to 'make -DNO_KERBEROS -DNO_WERROR
buildworld', and never saw miscellaneous switches passed. So, yeah, it
worked only after I unset CFLAGS and CXXFLAGS for that session's
environment.
Like I said, I'm generally new to this. Not so much FreeBSD as why
something on that level was breaking.
I didn't set -e, and didn't see it miscellaneously set someplace, so
could this be a bug that I stumbled across? That was using the
5.1-RELEASE version of make to do that buildworld of CURRENT, so I'll
have to check later if it has similar behavior with CURRENT's make.

On Sat, 2003-08-02 at 10:23, Ruslan Ermilov wrote:
> On Fri, Aug 01, 2003 at 11:08:33PM -0700, Peorth wrote:
> > That seems so weird.
> > CFLAGS and CXXFLAGS were set to something in the general environment,
> > for non-port builds, but I thought the FreeBSD make system used for
> > ports and such wouldn't get polluted by simply having that defined as a
> > variable in the env. *headscratch* Maybe just my mistake, but thanks a
> > lot. I never would've realized it was CFLAGS! Perhaps make should warn
> > if setting CFLAGS/CXXFLAGS are going to pollute, at least on certain
> > things like in the /usr/src tree, though up 'till that point, everything
> > built fine, too. *shrug*
> > 
> Hmm.  From the make(1) manpage:
> 
> : The four different classes of variables (in order of increasing prece-
> : dence) are:
> : 
> : Environment variables
> :      Variables defined as part of make's environment.
> : 
> : Global variables
> :      Variables defined in the makefile or in included makefiles.
> : 
> : Command line variables
> :      Variables defined as part of the command line.
> : 
> : Local variables
> :      Variables that are defined specific to a certain target.  The
> :      seven local variables are as follows:
> 
> Are you telling me that setting CFLAGS in the ENVIRONMENT causes
> this strange behavior?  (I cannot reproduce it here, because
> environment variables are of a lower precedence than globals.)
> 
> Are you sure you weren't running make(1) with the -e option?
> (I can reproduce this with this option, as it causes environment
> variables to take higher precedence than globals.)
> 
> 
> Cheers,