From: Leo Famulari <leo@famulari.name>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 32360@debbugs.gnu.org
Subject: bug#32360: gst-plugins-base has test failures (when built as a dependency)
Date: Fri, 17 Aug 2018 13:16:42 -0400 [thread overview]
Message-ID: <20180817171642.GA4821@jasmine.lan> (raw)
In-Reply-To: <20180803133858.0d6f5ac3@alma-ubu>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Fri, Aug 03, 2018 at 01:38:58PM +0200, Björn Höfling wrote:
> What I find strange is that the derivation of gst-plugins-base differs
> from the one above when directly building gst-plugins-base. That would
> make sense to me if there would be two packages of gst-plugins-base,
> like an inherited one or just any kind of copy. But here, the package
> definition of wine ist just using the "normal" package. Or have I
> overlooked something? Have I misunderstood something about derivations
> here?!
Presumably, you are using an x86_64 computer, and the successful build
of gst-plugins-base is for an x86_64-linux system. However, the wine
package and its dependency graph is always built as 32-bit software,
regardless of the underlying architecture:
From gnu/packages/wine.scm:
------
(arguments
`(;; Force a 32-bit build targeting a similar architecture, i.e.:
;; armhf for armhf/aarch64, i686 for i686/x86_64.
#:system ,@(match (%current-system)
((or "armhf-linux" "aarch64-linux")
`("armhf-linux"))
(_
`("i686-linux")))
------
And the test failure in the 32-bit build of gst-plugins base was
previously discussed on help-guix (no bug report):
https://lists.gnu.org/archive/html/help-guix/2018-06/msg00075.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-17 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:38 bug#32360: gst-plugins-base has test failures (when built as a dependency) Björn Höfling
2018-08-17 17:16 ` Leo Famulari [this message]
2018-08-17 18:05 ` Leo Famulari
2018-08-17 21:50 ` Björn Höfling
2018-08-18 10:46 ` Pjotr Prins
2018-08-18 11:34 ` Tobias Geerinckx-Rice
2018-08-19 7:35 ` Pjotr Prins
2018-08-18 7:44 ` 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=20180817171642.GA4821@jasmine.lan \
--to=leo@famulari.name \
--cc=32360@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
/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).