From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux. Date: Fri, 13 Oct 2017 20:38:13 -0400 Message-ID: <87y3oeh8cq.fsf@netris.org> References: <20171012173828.26257.23460@vcs0.savannah.gnu.org> <20171012173830.72AE320339@vcs0.savannah.gnu.org> <87tvz36elv.fsf@netris.org> <87r2u76qnr.fsf@fastmail.com> <87po9rhtpd.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41295) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3ATQ-000372-KU for guix-devel@gnu.org; Fri, 13 Oct 2017 20:38:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3ATL-00064Q-P3 for guix-devel@gnu.org; Fri, 13 Oct 2017 20:38:40 -0400 Received: from world.peace.net ([50.252.239.5]:47040) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e3ATL-00063U-KK for guix-devel@gnu.org; Fri, 13 Oct 2017 20:38:35 -0400 In-Reply-To: <87po9rhtpd.fsf@netris.org> (Mark H. Weaver's message of "Fri, 13 Oct 2017 12:57:02 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org Mark H Weaver writes: > Marius Bakke writes: > >> Note that mesa and libdrm did not build any drivers at all on armhf >> until recent commits on 'staging'. I tried cross-compiling libdrm >> to update etnaviv symbols instead, but failed some packages before it. >> >> So currently it's a trial-and-error process to find flags to make mesa >> build on armhf. This means armhf users are currently unable to build >> *any* graphical packages, actually. Given how expensive evaluations >> are, I figured we might as well deal with it on 'master'. > > Thanks for explaining. I think this should have been dealt with on the > 'staging' branch before merging into 'master'. This is a pretty bad > situation now for anyone using Guix on armhf. Didn't we already talk about this when you merged an earlier 'staging' branch into 'master' that contained a major GNOME upgrade that was untested, and broke GNOME desktops for all platforms? Do you think it should be acceptable to merge a major branch into 'master' where *all* graphical packages are broken on armhf? Do the Guix maintainers think that this is acceptable behavior? If so, where does that leave armhf users? Mark