From owner-freebsd-stable@freebsd.org Mon Mar 4 18:04:12 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 093E6151CEC4; Mon, 4 Mar 2019 18:04:12 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EE5F76BA4; Mon, 4 Mar 2019 18:04:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E2A6D23156; Mon, 4 Mar 2019 13:04:10 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 04 Mar 2019 13:04:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=3F635tW4bZKyhWVC1IcmoTc8FAK 6cP4svPZHO/VX5F4=; b=q2FjFV8SCqLzRzO6nxhp/ZV5l8DKEem8OtoaEPElAdH cmuaT9FSQgGm+m8jp5DAjrb+Xq0Xip43FgyoPZgT53wiL3qPkK5L+264I3fXCNdH skMJ0QMx5iyefeCO+13xz9Kp8Uh7dbI3Oa3tRMiPfxGktj+RZFhXIChDDdwnjKWE E4aOTMctFJ40EYXyvHmEoQFxTKahqcyMJA8XlrWd1gY+HJmFjQn2sS+xiJGC/FiT lvDizfX2jvFXgIolTgn1o9aYRYts47AHQYNe9WriJXJS6mM3hK0TPYZOWlvcEcg6 /dWLhHGHUyJi6LaANgGQLemegX09LPVaCQGxMYGTu1w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=3F635t W4bZKyhWVC1IcmoTc8FAK6cP4svPZHO/VX5F4=; b=AH9BS7y9znzoQc/YaENq+H 5bGywQf2bWzvLKnIYprnWRmsYf59XIAtznE0eAP3NVygjlWLc9emRLBCogq/ZdD5 lUw6O09FXxRBkz/XsYC3MlOKYl4mZ9QUQooY+TlS23zqyr9RL0jhtdukJ5K0U/K8 TimUv5+77y7ugTy7xy7GPFAghAyT7DShck/+QM8WgROavp1yr77+HN/eoNpvPv9R Iyus/vPHJl49/4vtAI/DfyugbqaKppOGPzmv9y/uoK8/RVOZFNZmcTgVoBBHO8Du ab7qW7Ot56upIClfPOUK4K6SUrQRSkJcHMGskBUQQcs+s1y/208zYWDpKn0Ly7MA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfedugddutdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttd ertddtredvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshes iiihgihsthdrnhgvtheqnecukfhppeekvddrjedtrdeluddruddtudenucfrrghrrghmpe hmrghilhhfrhhomhepthgvtghhqdhlihhsthhsseiihiigshhtrdhnvghtnecuvehluhhs thgvrhfuihiivgeptd X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id E8BCC10340; Mon, 4 Mar 2019 13:04:09 -0500 (EST) Date: Mon, 4 Mar 2019 18:04:07 +0000 From: tech-lists To: freebsd-arm@freebsd.org, freebsd-stable@freebsd.org Subject: Re: possibly silly binmiscctl question Message-ID: <20190304180407.GC46091@rpi3.zyxst.net> Mail-Followup-To: freebsd-arm@freebsd.org, freebsd-stable@freebsd.org References: <20190304175001.GB46091@rpi3.zyxst.net> <20190304175301.GA47280@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190304175301.GA47280@home.opsec.eu> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 9EE5F76BA4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.97)[-0.968,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 18:04:12 -0000 On Mon, Mar 04, 2019 at 06:53:01PM +0100, Kurt Jaeger wrote: >Hi! > >> If I give binmiscctl the magic for arm6 and then for say mips64, will >> this break things? >> >> Let's say I'm using an amd64 box to cross-compile using poudriere >> for arm6 and mips64 ports. Can I do both on the same box at the same >> time? Or do I need to let's say the arm6 run to finish, then give >> binmiscctl >> its magic strings for mips64, and THEN run the build run for that arch? > >I used two archs in parallel in the past, that was no problem. oh that's great news, thanks (really I should have made sure before doing it, lol!) -- J.