From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, guix-devel@gnu.org
Subject: Re: Error cross-compiling Mesa: failing test
Date: Sat, 07 Sep 2019 16:58:25 +0200 [thread overview]
Message-ID: <87a7bggnla.fsf@devup.no> (raw)
In-Reply-To: <87ftl9z1e8.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Hi!
>
> Our current `mesa' package has this bit:
>
> --8<---------------cut here---------------start------------->8---
> ,@(if (string-prefix? "i686" (%current-system))
> ;; Disable new test from Mesa 19 that fails on i686. Upstream
> ;; report: <https://bugs.freedesktop.org/show_bug.cgi?id=110612>.
> `((add-after 'unpack 'disable-failing-test
> (lambda _
> (substitute* "src/gallium/tests/unit/meson.build"
> (("'u_format_test',") ""))
> #t)))
> '())
> --8<---------------cut here---------------end--------------->8---
>
> When I attempt to cross-compile the package from x86-64 to x686, the
> faulty test is not disabled and the check phase fails.
>
> If I turn (%current-system) to (%current-target-system) it works.
> Should we update the package to use (%current-target-system) then?
I did not expect anyone to run tests when cross-compiling :-)
I think gnu-build-system disables tests in that case, but perhaps it
should not?
In any case you can change (%current-system) to:
(or (%current-target-system) (%current-system))
...and it should work. Feel free to push this change to 'master' :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-07 14:58 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7bggnla.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.