From: Mark H Weaver <mhw@netris.org>
To: 15392@debbugs.gnu.org
Subject: bug#15392: xorg-server FTBFS
Date: Mon, 16 Sep 2013 03:38:01 -0400 [thread overview]
Message-ID: <87wqmhgqsm.fsf@tines.lan> (raw)
In-Reply-To: <871u4pi625.fsf@tines.lan> (Mark H. Weaver's message of "Mon, 16 Sep 2013 03:22:58 -0400")
Mark H Weaver <mhw@netris.org> writes:
> xorg-server fails to build from source. See below for the tail of the
> build log. This is with aae4ead8142d4fd7c674a1e6e302f40469f878c6.
Sorry, the build log tail I posted was actually from a slightly modified
xorg.scm, where I uncommented the build inputs for 'xkbutils' and
'xkeyboard-config' in the 'xorg-server' recipe. Here's a corrected
version of the build log, using a pristine copy of
aae4ead8142d4fd7c674a1e6e302f40469f878c6. The only differences are in
the nix hashes.
Mark
--8<---------------cut here---------------start------------->8---
PASS: input
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
Fatal server error:
Failed to activate core devices.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
FAIL: xtest
PASS: misc
PASS: fixes
PASS: xfree86
========================================================================
1 of 9 tests failed
Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
========================================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/tmp/nix-build-xorg-server-1.12.2.drv-0/xorg-server-1.12.2/test'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/tmp/nix-build-xorg-server-1.12.2.drv-0/xorg-server-1.12.2/test'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/tmp/nix-build-xorg-server-1.12.2.drv-0/xorg-server-1.12.2/test'
make: *** [check-recursive] Error 1
phase `check' failed after 3 seconds
builder for `/nix/store/pjla94lqhahnrb0z2h05sb1zh8dlb9wp-xorg-server-1.12.2.drv' failed with exit code 1
@ build-failed /nix/store/pjla94lqhahnrb0z2h05sb1zh8dlb9wp-xorg-server-1.12.2.drv - 1 builder for `/nix/store/pjla94lqhahnrb0z2h05sb1zh8dlb9wp-xorg-server-1.12.2.drv' failed with exit code 1
guix package: error: build failed: build of `/nix/store/pjla94lqhahnrb0z2h05sb1zh8dlb9wp-xorg-server-1.12.2.drv' failed
--8<---------------cut here---------------end--------------->8---
next prev parent reply other threads:[~2013-09-16 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 7:22 bug#15392: xorg-server FTBFS Mark H Weaver
2013-09-16 7:38 ` Mark H Weaver [this message]
2013-09-16 13:27 ` Ludovic Courtès
2013-09-21 17:23 ` Andreas Enge
2013-09-21 20:02 ` Ludovic Courtès
2013-09-22 9:01 ` Andreas Enge
2013-09-22 9:09 ` Andreas Enge
2013-09-22 20:35 ` Ludovic Courtès
2013-09-23 17:22 ` Andreas Enge
2013-09-23 19:39 ` Ludovic Courtès
2013-09-25 7:00 ` Andreas Enge
2013-09-25 13:11 ` Ludovic Courtès
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=87wqmhgqsm.fsf@tines.lan \
--to=mhw@netris.org \
--cc=15392@debbugs.gnu.org \
/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).