From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.
Date: Fri, 13 Oct 2017 20:38:13 -0400 [thread overview]
Message-ID: <87y3oeh8cq.fsf@netris.org> (raw)
In-Reply-To: <87po9rhtpd.fsf@netris.org> (Mark H. Weaver's message of "Fri, 13 Oct 2017 12:57:02 -0400")
Mark H Weaver <mhw@netris.org> writes:
> Marius Bakke <mbakke@fastmail.com> 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
next prev parent reply other threads:[~2017-10-14 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171012173828.26257.23460@vcs0.savannah.gnu.org>
[not found] ` <20171012173830.72AE320339@vcs0.savannah.gnu.org>
2017-10-13 1:06 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Mark H Weaver
2017-10-13 14:58 ` Marius Bakke
2017-10-13 16:57 ` Mark H Weaver
2017-10-14 0:38 ` Mark H Weaver [this message]
2017-10-14 10:30 ` Marius Bakke
2017-10-16 12:56 ` Ludovic Courtès
2017-10-16 21:52 ` Leo Famulari
2017-10-17 16:08 ` Cuirass HTTP API Ludovic Courtès
2017-10-17 19:49 ` Ricardo Wurmus
2017-10-14 17:51 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Leo Famulari
2017-10-18 13:53 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3oeh8cq.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).