From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 105] New: menuconfig segfaults on tinyx if wchar is not selected
Date: Fri, 13 Feb 2009 02:40:08 +0000 (UTC) [thread overview]
Message-ID: <bug-105-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=105
Host: PC
Target: Any
Build: 02.2009
Summary: menuconfig segfaults on tinyx if wchar is not selected
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P3
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: frankhoeflich at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
To reproduce:
1. Get a fresh 02.2009 buildroot.
2. make menuconfig
3. Navigate to Graphic Libraries and applications
4. Navigate to X Window System server
5. Select tinyx. Boom.
My screenshot with error message from Kconfig is attached. The message is:
/bin/sh: line 4: 16472 Segmentation fault
KCONFIG_AUTOCONFIG=package/config/buildroot-config/auto.conf
KCONFIG_AUTOHEADER=package/config/buildroot-config/autoconf.h
package/config/mconf Config.in
If you select wchar in Toolchain between steps 2 and 3, tinyx is selected
normally.
--
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:[~2009-02-13 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 2:40 bugzilla at busybox.net [this message]
2009-02-13 2:58 ` [Buildroot] [Bug 105] menuconfig segfaults on tinyx if wchar is not selected bugzilla at busybox.net
2009-02-13 9:14 ` bugzilla at busybox.net
2009-02-13 9:18 ` bugzilla at busybox.net
2009-05-04 10:00 ` 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-105-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox