From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: bug-guile-sdl@gnu.org, 22020@debbugs.gnu.org
Subject: bug#22020: guile-sdl-0.5.2 fails to install on i686
Date: Sun, 17 May 2020 15:05:48 +0300 [thread overview]
Message-ID: <20200517120548.GD31833@E5400> (raw)
In-Reply-To: <87k11eiepr.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
On Thu, May 14, 2020 at 07:55:12PM +0200, Ricardo Wurmus wrote:
> Guile SDL 0.5.2 still fails on i686:
>
> --8<---------------cut here---------------start------------->8---
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Internal error: Could not resolve keysym XF86FullScreen
> Errors from xkbcomp are not fatal to the X server
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Internal error: Could not resolve keysym XF86FullScreen
> Errors from xkbcomp are not fatal to the X server
> /gnu/store/v1g7f3p4f0851mywrla8qmr9hb8jgfjr-bash-minimal-5.0.16/bin/bash: line 5: 6964 Segmentation fault HAVE_TTF=1 HAVE_MIXER=0 sh zow ${dir}$tst
> FAIL: gfx.scm
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Internal error: Could not resolve keysym XF86FullScreen
> Errors from xkbcomp are not fatal to the X server
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Internal error: Could not resolve keysym XF86FullScreen
> Errors from xkbcomp are not fatal to the X server
> PASS: fading.scm
> ======================================
> 1 of 8 tests failed
> (3 tests were not run)
> Please report to bug-guile-sdl@gnu.org
> ======================================
> --8<---------------cut here---------------end--------------->8---
>
> I’m putting bug-guile-sdl@gnu.org in Cc, hoping that this time our
> message can be delivered.
>
> If this doesn’t work we should mark this package unsupported for
> i686-linux.
>
> --
> Ricardo
>
I also took a look at this package last week and I saw it still failed
the tests on i686-linux. I would like to note, however, that it does
build and pass the test suite on powerpc-linux.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-17 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 22:31 bug#22020: guile-sdl-0.5.2 fails to install on i686 Luis Felipe López Acevedo
2015-11-29 11:49 ` bug#22020: Guile-SDL 0.5.2 test failure i686-linux-gnu Ludovic Courtès
2016-02-05 13:13 ` Ludovic Courtès
2020-05-14 17:55 ` bug#22020: guile-sdl-0.5.2 fails to install on i686 Ricardo Wurmus
2020-05-17 12:05 ` Efraim Flashner [this message]
2022-06-19 22:59 ` bug#22020: [PATCH] gnu: guile-sdl: Update to 0.6.1 Thiago Jung Bauermann via Bug reports for GNU Guix
2022-09-01 13:07 ` Efraim Flashner
2022-09-03 2:58 ` Thiago Jung Bauermann via Bug reports for GNU Guix
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=20200517120548.GD31833@E5400 \
--to=efraim@flashner.co.il \
--cc=22020@debbugs.gnu.org \
--cc=bug-guile-sdl@gnu.org \
--cc=rekado@elephly.net \
/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).