From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2965] New: Broken linkage to xkbcomp (blocking X server startup)
Date: Tue, 14 Dec 2010 22:48:12 +0000 (UTC) [thread overview]
Message-ID: <bug-2965-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2965
Summary: Broken linkage to xkbcomp (blocking X server startup)
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: adm at mpscompany.pl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hello,
Buildroot generates rootfs image with xkbcomp file is a sym link to host
xkbcomp binary.
[dynia at entropia images]$ tar tvf rootfs.tar | grep /usr/share/X11/xkb/xkbcomp
lrwxrwxrwx root/root 0 2010-12-14 20:24 ./usr/share/X11/xkb/xkbcomp ->
/mnt/b/Arm/buildroot-2010.11/output/host/usr/bin/xkbcomp
So in my case I got ARM rootfs link to non-existing and wrong (since x86)
binary.
Additionally I guest the xkbcomp is placed in a wrong dir since X server is
searching it in /usr/bin and the broken link is located in /usr/share/X11/xkb -
but this is rather a minor issue.
This have been tested on buildroot-2010.11 and daily snapshot at 15th Dec 2010.
Regards
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-12-14 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 22:48 bugzilla at busybox.net [this message]
2010-12-22 9:10 ` [Buildroot] [Bug 2965] Broken linkage to xkbcomp (blocking X server startup) bugzilla at busybox.net
2010-12-22 9:34 ` bugzilla at busybox.net
2010-12-22 21:07 ` bugzilla at busybox.net
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=bug-2965-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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.
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.