From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Leo Famulari <leo@famulari.name>
Cc: 32360@debbugs.gnu.org
Subject: bug#32360: gst-plugins-base has test failures (when built as a dependency)
Date: Fri, 17 Aug 2018 23:50:41 +0200 [thread overview]
Message-ID: <20180817235041.463c2723@alma-ubu> (raw)
In-Reply-To: <20180817180554.GB15789@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi Leo,
On Fri, 17 Aug 2018 14:05:54 -0400
Leo Famulari <leo@famulari.name> wrote:
> Here is a patch that excludes Opus when building gst-plugins-base on
> and for 32-bit systems. I think it's not so bad to be missing support
> for Opus in this context until the underlying bug is fixed.
>
> With this patch, gst-plugins-base builds successfully with
> '--system=i686-linux'. I didn't test the full Wine build.
I don't who/which program needs opus. But it's not working anyway, so I
would be fine with the patch.
I could not apply the patch. Maybe I did something wrong on my side?
Anyway, it's so short, I "applied" it manually.
Then it looks good:
$ ./pre-inst-env guix environment -C --expose=/gnu/store/ --ad-hoc wine
-- wine $(./pre-inst-env guix build hello --target=i686-w64-mingw32)/bin/hello.exe
[... some wine error message I suppose to be due to the -C
environment ...]
Hello, world!
Guix is so cool :-)
Thanks,
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-08-17 21:51 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
2018-08-17 18:05 ` Leo Famulari
2018-08-17 21:50 ` Björn Höfling [this message]
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=20180817235041.463c2723@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=32360@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).