From: Matt Wood <mattwood2000@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] make menuconfig fails - festival??
Date: Sat, 06 Sep 2008 20:12:10 +0200 [thread overview]
Message-ID: <20080906181210.248920@gmx.net> (raw)
I just checked out the latest snapshot of buildroot and when I try to run make menuconfig, I get the following error:
...
...
...
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE -g -O2 mconf.o zconf.tab.o lxdialog/checklist.o lxdialog/util.o lxdialog/inputbox.o lxdialog/textbox.o lxdialog/yesno.o lxdialog/menubox.o -lncursesw -o mconf
make[1]: Leaving directory `/usr/arm/buildroot/package/config'
target/device/KwikByte/Config.in:78 warning: Overlong line
toolchain/external-toolchain/Config.in:17 warning: Overlong line
package/ipsec-tools/Config.in:7 warning: Overlong line
package/audio/festival/Config.in:11: can't open file "package/festival/speech-tools/Config.in"
Any ideas? Thanks, Matt.
--
GMX Kostenlose Spiele: Einfach online spielen und Spa? haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196
next reply other threads:[~2008-09-06 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 18:12 Matt Wood [this message]
2008-09-06 18:30 ` [Buildroot] make menuconfig fails - festival?? Markus Heidelberg
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=20080906181210.248920@gmx.net \
--to=mattwood2000@gmx.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