From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 018E6C3ABBF for ; Wed, 7 May 2025 20:43:16 +0000 (UTC) Received: from lelvem-ot01.ext.ti.com (lelvem-ot01.ext.ti.com [198.47.23.234]) by mx.groups.io with SMTP id smtpd.web10.6443.1746650591477522239 for ; Wed, 07 May 2025 13:43:11 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=WQcrAaO1; spf=pass (domain: ti.com, ip: 198.47.23.234, mailfrom: rs@ti.com) Received: from fllv0035.itg.ti.com ([10.64.41.0]) by lelvem-ot01.ext.ti.com (8.15.2/8.15.2) with ESMTPS id 547KgpkY905833 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 May 2025 15:42:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1746650571; bh=KH7oGZJTg3VfwRgQYapPZRrVFbK75eDu09JKCNuC74M=; h=Date:CC:Subject:From:To:References:In-Reply-To; b=WQcrAaO1VzqjqHZ8FLU2j8GbdvP3I88qL2VsgP6P0UAZTRvHgoGk2H82LuFZqA0xb K33dcHVpGyy+VOLtwEwK3qd/aAGhKJGC8N5j7HlHHKcUV0vZh4sZDhRJEhlIeiVM/P Jp3zWApfojTvdcwD8UIoiWBLuOohpPkf/24pY80o= Received: from DLEE109.ent.ti.com (dlee109.ent.ti.com [157.170.170.41]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 547KgpLi122159 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 7 May 2025 15:42:51 -0500 Received: from DLEE111.ent.ti.com (157.170.170.22) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 7 May 2025 15:42:50 -0500 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DLEE111.ent.ti.com (157.170.170.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 7 May 2025 15:42:50 -0500 Received: from localhost (rs-desk.dhcp.ti.com [128.247.81.144]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 547KgouT094068; Wed, 7 May 2025 15:42:50 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Date: Wed, 7 May 2025 15:42:50 -0500 Message-ID: CC: Mathieu Dubois-Briand , , , , , , , , , , , Subject: Re: [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland From: Randolph Sapp To: Alexander Kanavin X-Mailer: aerc 0.20.1-0-g2ecb8770224a References: <20250505224801.3181046-1-rs@ti.com> In-Reply-To: X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 07 May 2025 20:43:16 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/216134 On Wed May 7, 2025 at 8:37 AM CDT, Alexander Kanavin wrote: > On Wed, 7 May 2025 at 01:03, Randolph Sapp via lists.openembedded.org > wrote: > >> Ah, this is the first I hearing about the gnux32 triplet. Well, that is = being >> filtered out by COMPATIBLE_HOST in the goarch bbclass. Some of those val= ues seem >> to be invalid now (powerpc64 is supported upstream). That being said, I = don't >> see any mention of the new x32 ABI upstream. Not entirely sure how to ad= dress >> that at the moment. > > There are two options: > > - set up the x32 build as specified in [1], replicate the fail, tweak > COMPATIBLE_HOST as needed (in a separate commit) and see if any > further issues come up. > > - correct [1] to no longer build core-image-sato for x32, and replace > it with core-image-full-cmdline, reducing x32 to non-graphical > targets. It's been a controversial target for a long time, as no one > has ever seen actual usage of it, and there's been a stream of > graphical related crashes and build failures. We keep it around for > now, but I'd fully support dropping the graphics and leaving only the > console images. > > [1] https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.jso= n#n867 > > Alex Alright, well I did a little work poking around go. It has no understanding= of the x32 ABI currently. Dropping the x32 tests from core-image-sato to core-image-full-cmdline can work, but that does mask a bit of a regression. As useful as a display manager will be, I'm not sure I can justify that muc= h of a regression for an entire ABI. I know the linux kernel has debated about dropping x32 support a number of times, GCC seems to be the only compiler t= hat has fully implemented it, and Yocto is one of 3 listed distro solutions tha= t currently support it. Still feels a little rough. I don't know. Anyone got any strong opinions here?