[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.

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
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Mark H Weaver <address@hidden> writes:

> Marius Bakke <address@hidden> 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?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]