>Number:         19823
>Category:       toolchain
>Synopsis:       BUILDING states MKOBJDIRS defaults to 'yes', which is actually 'no'
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    toolchain-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 12 12:28:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     OGAWA Takaya
>Release:        1.6L
>Organization:
>Environment:
NetBSD aragorn.middle.earth 1.6L NetBSD 1.6L (ARAGORN) #11: Sun Jan 12 23:06:58 JST 2003     t-ogawa@aragorn.middle.earth:/sys/arch/i386/compile/ARAGORN i386

>Description:
In BUILDING, it clearly states:

     MKOBJDIRS        Can be set to ``yes'' or ``no''.  Indicates whether ob-
                      ject directories will be created automatically (via a
                      ``make obj'' pass) at the start of a build.

                      Default: ``yes''

This is true when you build via build.sh, because the script automatically
set the value to 'yes'.  However, this is not the case if you invoke
'make' directly without using build.sh since there is a line in
share/mk/bsd.own.mk:

MKOBJDIRS:=  no

Since the default value in bsd.own.mk hasn't been changed since 1999,
I qualify the document has some kind of mistake.

>How-To-Repeat:

>Fix:
How about changing like this?

--- doc/BUILDING.mdoc   4 Jan 2003 12:55:33 -0000       1.8
+++ doc/BUILDING.mdoc   12 Jan 2003 20:26:34 -0000
@@ -532,7 +532,7 @@
 (via a
 .Dq make obj
 pass) at the start of a build.
-.DFLTy
+.DFLTn
 .
 .It Sy NBUILDJOBS
 Now obsolete.
@@ -983,6 +983,8 @@
 .Sy MKOBJDIRS
 to
 .Dq no .
+Otherwise, it will be automatically set to
+.Dq yes .
 .
 .It Fl R Ar rel
 Set the value of


>Release-Note:
>Audit-Trail:
>Unformatted: