From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2845] New: dialog 1.1 needs libtinfo from ncurses
Date: Wed, 17 Nov 2010 22:48:36 +0000 (UTC) [thread overview]
Message-ID: <bug-2845-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2845
Summary: dialog 1.1 needs libtinfo from ncurses
Product: buildroot
Version: 2009.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: sergio at sergiomb.no-ip.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
>>> dialog 1.1-20100428 Building
buildroot-2010.08/output/staging/usr/bin/mipsel-unknown-linux-uclibc-gcc
--sysroot=/buildroot-2010.08/output/staging -o dialog dialog.o -L. -ldialog
-Lbuildroot-2010.08/output/staging/lib
-Lbuildroot-2010.08/output/staging/usr/lib -lncurses -ltinfo -lm
buildroot-2010.08/output/staging/usr/lib/gcc/mipsel-unknown-linux-uclibc/4.3.5
/../../../../mipsel-unknown-linux-uclibc/bin/ld: cannot find -ltinfo
collect2: ld returned 1 exit status
--
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-11-17 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 22:48 bugzilla at busybox.net [this message]
2010-11-17 22:58 ` [Buildroot] [Bug 2845] dialog 1.1 needs libtinfo from ncurses bugzilla at busybox.net
2010-11-24 22:08 ` bugzilla at busybox.net
2010-11-25 4:54 ` bugzilla at busybox.net
2010-11-25 5:08 ` bugzilla at busybox.net
2010-11-25 10:26 ` bugzilla at busybox.net
2010-11-25 18:25 ` bugzilla at busybox.net
2010-11-26 8:35 ` bugzilla at busybox.net
2011-03-01 22:43 ` bugzilla at busybox.net
2011-03-01 22:45 ` 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-2845-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