Subject: Re: Build process and tunable vars, on we go.
To: Greywolf <greywolf@starwolf.com>
From: Martin Weber <Ephaeton@gmx.net>
List: current-users
Date: 11/22/2002 18:31:28
On Fri, Nov 22, 2002 at 08:51:05AM -0800, Greywolf wrote:
> On Fri, 22 Nov 2002, Martin Weber wrote:
> 
> # Yes, sure you won't find openssl/something.h, I said MKCRYPTO=no ...
> # *sigh* Fine, going to rebuild without MKCRYPTO setting now (although
> # it's nothing but a waste of space on my laptop, going to delete the
> # libs/programs by hand afterwards). It's frustrating to read about
> # tunable vars in src/BUILDING just to find out that you better don't
> # touch them if you _really_ want to build NetBSD.
> 
> The problem exists that some variables are of the defined/undefined
> toggle, while others are of the yes/no toggle.
> 
> What this means is that in all cases, VAR=yes will do what you expect,
> while VAR=no will mean "yes" in some cases and "no" in others.

Well, I trusted the src/BUILDING document. Check this out:

     MKCATPAGES  Can be set to ``yes'' or ``no''.  Indicates whether prefor-

     MKCRYPTO    Can be set to ``yes'' or ``no''.  Indicates whether crypto-

     MKDOC       Can be set to ``yes'' or ``no''.  Indicates whether system

     MKINFO      Can be set to ``yes'' or ``no''.  Indicates whether GNU Info

     MKMAN       Can be set to ``yes'' or ``no''.  Indicates whether manual

     MKNLS       Can be set to ``yes'' or ``no''.  Indicates whether Native

     MKOBJ       Can be set to ``yes'' or ``no''.  Indicates whether object

     MKPIC       Can be set to ``yes'' or ``no''.  Indicates whether shared

     MKPICINSTALL
                 Can be set to ``yes'' or ``no''.  Indicates whether the ar(1)

     MKPROFILE   Can be set to ``yes'' or ``no''.  Indicates whether profiled

> This should be addressed.  Pick one.

If it's a defined/undefined issue, well, then the documentation needs to
be adjusted, too.

> ...and it would be A Nice Thing to have a sample mk.conf in, probably,
> /usr/share/examples/make/mk.conf.

Well, I set those in the environment, as pointed out in src/BUILDING, that
would be enough:

CONFIGURATION
   Environment variables
     Several environment variables control the behaviour of NetBSD builds.
[... list of environment vars as above + more ...]

thanks for the answer though :)

-Martin