From nobody Tue Oct 03 14:54:53 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4S0LTN6dDDz4wKx0 for ; Tue, 3 Oct 2023 14:55:04 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Received: from mail.worldserver.net (mail.worldserver.net [217.13.200.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits)) (Client CN "*.worldserver.net", Issuer "EuropeanSSL Server CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S0LTJ6MBPz3MBX for ; Tue, 3 Oct 2023 14:55:00 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nebelschwaden.de header.s=1687803001 header.b=Lu+DuX26; spf=pass (mx1.freebsd.org: domain of listac@nebelschwaden.de designates 217.13.200.36 as permitted sender) smtp.mailfrom=listac@nebelschwaden.de; dmarc=none Received: from postpony.nebelschwaden.de (v22018114346177759.hotsrv.de [194.55.14.20]) (Authenticated sender: sendmail@nebelschwaden.de) by mail.worldserver.net (Postfix) with ESMTPSA id EE2271E0AF8 for ; Tue, 3 Oct 2023 16:54:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nebelschwaden.de; s=1687803001; t=1696344895; bh=eArtvXHIkntHMIaJNd7fVens4zcyMQQ5ll3ngiP+tOM=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To:From; b=Lu+DuX26OiC19mdKfxFzokTNsEe/95+RLWMAyObskNDaB+kHWHiluM74OVfVv3bTu 3Y7iBwjDdII/kAd6gNExP/kcn0kQ+dWegMABunnDKkXSEdtcXQFpYxX7PJD10g/NyG 9Ce94iHJ7ztrNkKDjxCb2OgQz7qSpRs8wgeGJuA+cR/mvkUMLvll0j/0O/J13sHvhK xN6LQQKFMHItdcSlruizwTeV40rhOyPsOCYU0tnkjS34yQxrRkjzSJmYNSsjMrFtdz 5GXb208pnT1watKWBQ/z9chS2nA2fXT6CqW8eP/EfKYMBdE6FiOya8481C4ouIguv6 PtsLKxjjGqvxw== Received: from [172.16.37.5] (kaperfahrt.nebelschwaden.de [172.16.37.5]) by postpony.nebelschwaden.de (Postfix) with ESMTP id 1467B113DD9 for ; Tue, 3 Oct 2023 16:54:54 +0200 (CEST) Message-ID: <6fe24942-f592-4213-b8a7-4e45cc08ae26@nebelschwaden.de> Date: Tue, 3 Oct 2023 16:54:53 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: listac@nebelschwaden.de Subject: Re: buildworld: specifying an alternate make.conf Content-Language: en-US To: questions@freebsd.org References: <4249ee95-5081-4d4d-943c-3a6948ba4af7@nebelschwaden.de> <3deea77b-2a84-469c-86f0-9c34ec3b0759@FreeBSD.org> From: Ede Wolf In-Reply-To: <3deea77b-2a84-469c-86f0-9c34ec3b0759@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.59 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+ip4:217.13.200.0/24]; R_DKIM_ALLOW(-0.20)[nebelschwaden.de:s=1687803001]; RCVD_IN_DNSWL_LOW(-0.10)[217.13.200.36:from]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[nebelschwaden.de]; HAS_REPLYTO(0.00)[listac@nebelschwaden.de]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15657, ipnet:217.13.192.0/20, country:DE]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DKIM_TRACE(0.00)[nebelschwaden.de:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4S0LTJ6MBPz3MBX Am 03.10.23 um 15:52 schrieb Matthew Seaman: > On 03/10/2023 13:48, Ede Wolf wrote: > >> to my understanding of man make and make.conf, which admittedly is >> very limited, I should be able to specify an alternate make.conf with >> this syntax: >> >> # make -D __MAKE_CONF=/make.conf buildworld >> >> Now, since this looks somewhat strage - nowhere else I have found make >> variables with double underscores - and before wasting hours of >> compiling, I am wondering, is above correct? Or did I miss[understand] >> anything? > > Adding a leading underscore to a variable name is a common idiom for > "this variable is implementation defined, do not mess with it."  Two > underscores re-emphasizes all that, and typically means the value is > considered private and internal -- useful in languages which have no > built-in capability to hide their internals. > > In your case, however, it seems that overriding __MAKE_CONF really is > the documented method of pointing your build environment at a different > make.conf file.  Presumably the concept was that almost everyone would > just edit /etc/make.conf to suit themselves, and almost no-one would > ever need to switch between alternative make.conf files. > > Note: if you're trying to configure building the base system, then you > probably want to customize /etc/src.conf as described in the src.conf(5) > man page.  There's a lot of overlap between make.conf and src.conf, but > make.conf also affects building ports whereas src.conf only applies to > building the base system. > >     Cheers, > >     Matthew > Hello Matthew, Thanks for the advise, this is what I am trying to archive, as I am using make.conf exactly to primarily point to another src.conf and src-env.conf (shortend, the full version is in another reply): # MAKE_SHELL?=sh SRCCONF=/data/admin/build/vbox/src.conf SRC_ENV_CONF=/data/admin/build/vbox/src-env.conf Basically I want all three {make,src,src-env}.conf to reside within the same folder (that is not /etc), one for each host this machine is buiding base for. However, it seems, my src-env.conf is not being honored, not sure about the contents of src.conf.