Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>
To: Dan Kegel <dank@kegel.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: Fri, 31 Oct 2003 17:41:00 -0000	[thread overview]
Message-ID: <200310311143.29532.ken.wolcott@med.ge.com> (raw)
In-Reply-To: <3FA18E26.8030309@kegel.com>

On Thursday 30 October 2003 16:18, Dan Kegel wrote:
> 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

Hi Dan;

  I'm trying to remember to append my replies to the bottom of existing msgs 
:-)

  I added -ex to my script.

  I looked at gdb configure and the resultant Makefile for the specific error 
string...it is very hard for me to follow :-(

looking for termcap in configure:
*******************************************************
grep termcap ../gdb-6.0/configure
    configdirs="$configdirs libtermcap" ;;
    target_configdirs="$target_configdirs target-libtermcap target-winsup"
*******************************************************

looking for termcap in Makefile generates lots of output, but in that output, 
library is not found:

****************************************
grep termcap Makefile | grep library
<no putput>
****************************************

I changed the make install line for ncurses compile script to point to the lib 
generated by crosstool.  Looks like the libraries were written there 
successfully.  But the gdb compile still fails for the same reason.

:-(

Ken


  reply	other threads:[~2003-10-31 17:41 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
2003-10-31 17:41   ` Wolcott, Ken (MED, Compuware) [this message]
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=200310311143.29532.ken.wolcott@med.ge.com \
    --to=ken.wolcott@med.ge.com \
    --cc=bug-ncurses@gnu.org \
    --cc=crossgcc@sources.redhat.com \
    --cc=dank@kegel.com \
    --cc=gdb@sources.redhat.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