From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 883681382C5 for ; Thu, 21 May 2020 00:19:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 93233E09DE; Thu, 21 May 2020 00:19:07 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2FF55E09DE for ; Thu, 21 May 2020 00:19:07 +0000 (UTC) Received: by mail-ej1-f54.google.com with SMTP id s3so6669534eji.6 for ; Wed, 20 May 2020 17:19:06 -0700 (PDT) X-Gm-Message-State: AOAM533Cr1G31YEWLY2pgWlWyKGnbdTgObho8i9CidQkM+09NhXdbTsj LaOgjLPX8oKBGNPoNXe/OGpE3Xi8pPzG0eRenlU= X-Google-Smtp-Source: ABdhPJyXDbilhUBlFcfgDLKaJyW6YpDbvMBUHc5u+CmhZL+y2adXHRL48krcGcwm2ycy1PdBFxIbiECcjnSUkA/bq/Y= X-Received: by 2002:a17:906:a1da:: with SMTP id bx26mr1494650ejb.42.1590020343192; Wed, 20 May 2020 17:19:03 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20200520034226.2870937-1-mattst88@gentoo.org> <20200520034226.2870937-19-mattst88@gentoo.org> <94424974-cfe8-9766-8712-ae6fa8bbf825@veremit.xyz> In-Reply-To: <94424974-cfe8-9766-8712-ae6fa8bbf825@veremit.xyz> From: Matt Turner Date: Wed, 20 May 2020 17:18:51 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-catalyst] [PATCH 19/21] catalyst: Set jobs/load-average via catalyst.conf To: "Michael 'veremitz' Everitt" Cc: gentoo-catalyst@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 4ed5fc5c-85d7-4918-9e10-93bdeb107541 X-Archives-Hash: dfff06e6b7b1a2fb5debdc8dbe67c626 On Wed, May 20, 2020 at 4:00 PM Michael 'veremitz' Everitt wrote: > > On 20/05/20 04:42, Matt Turner wrote: > > We currently have two mechanisms of setting MAKEOPTS: in spec files and > > in catalystrc. > > > > Setting makeopts in spec files doesn't make sense. The spec should > > describe the thing that's being built and not contain options that are > > specific to the build system. > > > > Setting makeopts via catalystrc is better, but it only applies to the > > actual build system invocations, leaving emerge to run jobs serially or > > again requiring configuration specific to the build machine to be put > > into the spec file. For example: > > > > update_seed_command: ... --jobs 5 --load-average 5 > > > > With jobs and load-average specified in catalyst.conf, catalyst has the > > information required to configure both emerge and the build systems > > emerge executes. > > > > This removes the undocumented makeopts spec file option and replaces it > > with jobs and load-average settings in catalyst.conf. > > > > Signed-off-by: Matt Turner > > --- > > catalyst/base/stagebase.py | 12 +++++------- > > catalyst/defaults.py | 2 ++ > > doc/catalyst-config.5.txt | 15 ++++++++++++--- > > etc/catalyst.conf | 8 ++++++++ > > etc/catalystrc | 3 --- > > targets/support/chroot-functions.sh | 8 ++++++++ > > 6 files changed, 35 insertions(+), 13 deletions(-) > NACK. This and patch 20 make it impossible to customise specs for different > arches/subarches/libc/etc using different distcc_hosts with varying numbers > of hosts and/or cores available. In many cases, you may not be able to set > up identical distcc 'farms' or 'clusters' with the complete set of > toolchains/chroots applicable to a 'standard' installation, due to hardware > limitations. I don't follow. You mention varying distcc hosts per arches/subarches/libc. Let's say there are 4 systems on the network. 3x amd64 systems and 1 mips system. If I'm compiling for amd64 on system and I'm using distcc, there's a fixed number of distcc hosts on the network, aren't there? If I'm building for mips on the mips system with cross compilers installed on, say two of the amd64 systems, then there's a fixed number of distcc hosts on the network, aren't there? So, I don't think arches (or subarches) has any bearing. And for different libcs, distcc doesn't have any bearing on that, does it? distcc (without pump mode, which has been removed from Gentoo) sends preprocessed source files across the network, so what libc you have doesn't have any bearing either. You seem to be thinking that setting a single system-wide distcc_hosts is somehow limiting, but I can't see how. Please explain.