From: Dan Kegel <dank@kegel.com>
To: "Wolcott, Ken (MED, Compuware)" <ken.wolcott@med.ge.com>
Cc: gdb mailing list <gdb@sources.redhat.com>,
crossgcc@sources.redhat.com,
ncurses mailing list <bug-ncurses@gnu.org>
Subject: Re: unable to build arm9 gdb lack of termcap, termcap not provided by ncurses, rather terminfo
Date: Thu, 30 Oct 2003 22:12:00 -0000 [thread overview]
Message-ID: <3FA18E26.8030309@kegel.com> (raw)
In-Reply-To: <200310301552.03913.ken.wolcott@med.ge.com>
Wolcott, Ken (MED, Compuware) wrote:
> I'm still unable to build an arm9 gdb using Dan Kegel's crosstool
> (http://www.kegel.com/crosstool/) and a patched (ncurses-5.3-20031025)
> ncurses-5.3 because it complains about a missing termcap. ncurses provides
> terminfo but I don't see a termcap. The patched ncurses-53 apparently builds
> successfully if I turn off ada language support. crosstool apparently builds
> the arm9 cross toolchain successfully. Perhaps I haven't placed the
> libraries generated by ncurses in the correct location for the gdb build to
> see them. I copied /tmp/ncurses/src/lib/* to the lib dir created by
> crosstool. Perhaps gdb configure needs to be told where to get libraries
> from? Bzip2'd output from the gdb build attempt and the script that
> initiates the build are attached.
(A couple tips:
add set -x to your build scripts in the future, makes the logs easier to read.
add set -e as well, so the script aborts at first error.)
The thing to do here is to read gdb's configure script to see where it is
outputting that error message, "configure: error: no termcap library found".
That will tell you how it's looking for the library.
Another thing you could do is use your cross-compiler to do a trivial program
that uses ncurses. If it doesn't compile, or doesn't link, you have
installed ncurses wrong.
If you copied the files by hand, you probably installed them wrong.
It's better form to use ncurses' "make install" rule to install the files.
You may need to override the destination directory when you do this.
To tell how to do this, either read the ncurses Makefile, or look
at how some other package cross-builds and installs ncurses. ptxdist
does the install step like this:
make DESTDIR=$(CROSS_LIB_DIR) prefix='' exec_prefix='' install
where CROSS_LIB_DIR is $(PTXCONF_PREFIX)/$(PTXCONF_GNU_TARGET)
or something like /opt/crosstool/$(TARGET)/$(TOOLCOMBO)/$(TARGET)
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next prev parent reply other threads:[~2003-10-30 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 21:49 Wolcott, Ken (MED, Compuware)
2003-10-30 22:12 ` Dan Kegel [this message]
2003-10-31 17:41 ` Wolcott, Ken (MED, Compuware)
2003-10-31 18:41 ` Dan Kegel
[not found] ` <20031030232655.GA15004@invisible-island.net>
2003-10-31 14:43 ` Wolcott, Ken (MED, Compuware)
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=3FA18E26.8030309@kegel.com \
--to=dank@kegel.com \
--cc=bug-ncurses@gnu.org \
--cc=crossgcc@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=ken.wolcott@med.ge.com \
/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