unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>,
	Jelle Licht <jlicht@fsfe.org>,
	guix-devel@gnu.org
Subject: Re: Error cross-compiling Mesa: failing test
Date: Fri, 27 Sep 2019 19:34:38 +0200	[thread overview]
Message-ID: <87a7apabip.fsf@devup.no> (raw)
In-Reply-To: <87h84xg61n.fsf@ambrevar.xyz>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> Marius: you told me to update master, but
>
> --8<---------------cut here---------------start------------->8---
>> guix refresh -l mesa
> Building the following 822 packages would ensure 1514 dependent packages are rebuilt:
> --8<---------------cut here---------------end--------------->8---
>
> I'd say this should go to staging.  Thoughts?

This change only affects i686 cross-builds of Mesa, because the
conditional is tested outside of the builder.  I.e. "guix build mesa"
should produce the same result before and after this change, even on
i686.  If that is the case, it is safe for 'master'.

I'm still not sure whether it is sensible for meson-build-system to run
tests when cross-compiling, but that is another story.  :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-09-27 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 19:10 Error cross-compiling Mesa: failing test Pierre Neidhardt
2019-09-07 14:58 ` Marius Bakke
2019-09-19 10:44   ` Pierre Neidhardt
2019-09-19 10:57     ` Jelle Licht
2019-09-19 10:59       ` Pierre Neidhardt
2019-09-19 11:05         ` Jelle Licht
2019-09-19 11:32           ` Pierre Neidhardt
2019-09-27 14:36             ` Pierre Neidhardt
2019-09-27 17:34               ` Marius Bakke [this message]
2019-10-03 10:04                 ` Pierre Neidhardt

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=87a7apabip.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=mail@ambrevar.xyz \
    /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).