From nobody Fri Mar 31 13:18:34 2023 X-Original-To: freebsd-current@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 4Pp1802lg2z42V4K for ; Fri, 31 Mar 2023 13:18:40 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pp17z4kGPz3xMs for ; Fri, 31 Mar 2023 13:18:39 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b="ezgljz/l"; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=QreSD7LF; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 0642F32008FF for ; Fri, 31 Mar 2023 09:18:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 31 Mar 2023 09:18:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1680268717; x=1680355117; bh=g6 32seqJ5RzCY8fUoE9H9Hx2zsz5FB+6q0zQsLBx/Bs=; b=ezgljz/lNZs+CsUU+D wVkpGD/TuqoLNbvcOH6tMXqXPzDu7Zx8+LsGwy1NDKnLVw0tCWDj+6CesHm1hWmE 7mrOlwcm9GMZL49u2nPX4LIXNccEAUqI2+3Smtflp6NuRcFjwGNQyVdrRY8WbMiA urAl/Fe6ikAIrHFzjWZ1chMtmaKt9d2itZ/hMUmHPXGIkRMvHYoH/qcphHYBWgr6 RkLOQIgYuvNSHTZFGFNdBUh9HFPST+lenbsJmHz9W0mP+UbJ4C/0hIw4oGK0x8B2 g00n/WYbr7dHCR65bC1XYhMPcx3OB1vWip6hXGcgCRlzGD2yWTPXsplF8TBTwDiM /PHQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1680268717; x=1680355117; bh=g632seqJ5RzCY 8fUoE9H9Hx2zsz5FB+6q0zQsLBx/Bs=; b=QreSD7LF5/Q97JHevEyGBFJzprHS/ u/soDgoApjFLUNxHvp1UObF8K74tmWyLR/jgs+uipb87GftTmMs6PwrYgDzpxt6P Jbc89Cm84FLI3GZpfxzlpALxkRtgj0HwUtlJVXVvWCjrONk/2EFqjgBhUsO+WL87 E9Fw7CjO0WCKEW08tY+UMJfi77/IrFw0HtVfBR3s6ZG3kJw5QOE16GVyaDUAFic2 B91IPpGbwN8zKQvCVlPy6/k+eqSsgKCbvYmcMuk/Hirn4n1x4Kc4b5YFAlOLynNu LFuik5KRR2coGpRO5b8LdBydSeRpYDiufU7WtqV3IIhnGzWJfkHy2Fd5A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeiuddgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 31 Mar 2023 09:18:37 -0400 (EDT) Date: Fri, 31 Mar 2023 14:18:34 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5') Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <2E3300BE-5D37-4476-B0CB-7D0ECAE06957.ref@yahoo.com> <2E3300BE-5D37-4476-B0CB-7D0ECAE06957@yahoo.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <2E3300BE-5D37-4476-B0CB-7D0ECAE06957@yahoo.com> X-Spamd-Result: default: False [-4.27 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.67)[-0.672]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pp17z4kGPz3xMs X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Thu, Mar 30, 2023 at 07:30:15PM -0700, Mark Millard wrote: >Warner Losh wrote on >Date: Thu, 30 Mar 2023 22:15:38 UTC : > >> On Thu, Mar 30, 2023, 3:45 PM void wrote: >> >> > On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote: >> > >> > >To my knowledge, FreeBSD has not actively supported newer >> > >FreeBSD building older FreeBSD across versions. >> > >> > Are you sure? I routinely build & run 12.4 and 12-stable bhyve and >> > poudriere jail instances on -current. >> > >Do you use main's toolchain to do your builds of releng/12.4 >and stable/12 ? The first time? Their updating builds? As far >as I can see use of main's toolchain means not using an older >user space (via/in-a chroot, jail, etc.) to do the builds. I don't know in detail about the toolchain. When 12.4 builds on -current, the screen shows it bootstrapping, and I guess this is for 12.4. The reason I commented on what you wrote was because your assertion appeared to me[1] to be incorrect, in that logically following on from that assertion would mean 'don't expect it to work because it's 'not actively supported' meaning that it's 'unsupported'. But I can't contextualise 'actively supported' into 'should work' or 'expected to work' given Warren's comment about 'best effort basis'. I build poudriere jails for 12.4 on -current like so: 1. git -C /usr/src checkout releng/12.4 2. poudriere jail -c -j 124Ramd64 -J12 -m src=/usr/src -b -v releng/12.4 To update: 3. git -C /usr/src checkout releng/12.4 4. git -C /usr/src pull --ff-only 5. then I have to delete and build the jail as in [2] otherwise it'll complain about wrong objectprefix is this workflow incorrect? >A sequence can be bootstrapped by starting from materials for >a pre-built release or snapshot of the older user space and >then update via its internal toolchain. My understanding is >this is the actively supported way, not building older >user spaces directly from a newer user space and its >newer toolchain. It appears to me[1] to be building its own toolchain and building within that. The ports it builds work on the machine it's built for, without errors about things like ABI etc. I don't do any pre-building, and am unsure if the poudriere jailbuilding process does anything outside of the standard build process. [1] non-expert in any of this! --