From: Johannes Berg <johannes@sipsolutions.net>
To: "Anh K. Huynh" <kyanh@viettug.org>
Cc: backports@vger.kernel.org
Subject: Re: Buid backports-20130528 on ArchLinux: /usr/bin/ld: cannot find -ltinfo
Date: Sun, 02 Jun 2013 19:41:39 +0200 [thread overview]
Message-ID: <1370194899.8366.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130602220934.3079ee4f@icy> (sfid-20130602_170957_728483_48913C26)
On Sun, 2013-06-02 at 22:09 +0700, Anh K. Huynh wrote:
> Hello,
>
> I'm building the `backports-20130528` on ArchLinux (kernel = 3.2.46).
> I see the error as in http://pastie.org/7996763 .
>
> I don't have any problem when building the new Linux kernel. When I
> remove the `tinfo` support from the file `kconf/Makefile` I can run
> `make menuconfig` perfectly.
>
> Is the `tinfo` library really needed to run `make menuconfig` when
> building backports drivers?
It was needed on some distros, and not on others. This is probably the
best option?
diff --git a/backport/kconf/Makefile b/backport/kconf/Makefile
index ff5c270..dfd793a 100644
--- a/backport/kconf/Makefile
+++ b/backport/kconf/Makefile
@@ -3,7 +3,7 @@ CFLAGS=-Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer
LXDIALOG := lxdialog/checklist.o lxdialog/inputbox.o lxdialog/menubox.o lxdialog/textbox.o lxdialog/util.o lxdialog/yesno.o
conf: conf.o zconf.tab.o
-mconf: LDFLAGS = -Wl,--no-as-needed -lncurses -ltinfo
+mconf: LDFLAGS = -Wl,--no-as-needed $(shell ./lxdialog/check-lxdialog.sh -ldflags $(CC))
mconf: CFLAGS += -DCURSES_LOC="<ncurses.h>" -DLOCALE
mconf: mconf.o zconf.tab.o $(LXDIALOG)
johannes
next prev parent reply other threads:[~2013-06-02 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 15:09 Buid backports-20130528 on ArchLinux: /usr/bin/ld: cannot find -ltinfo Anh K. Huynh
2013-06-02 17:41 ` Johannes Berg [this message]
2013-06-03 3:18 ` Anh K. Huynh
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=1370194899.8366.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=kyanh@viettug.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.
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.