Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>
To: dickey@his.com
Cc: gdb mailing list <gdb@sources.redhat.com>
Subject: Re: unable to build arm9 gdb lack of termcap, termcap not provided by ncurses, rather terminfo
Date: Fri, 31 Oct 2003 14:43:00 -0000	[thread overview]
Message-ID: <200310310845.35490.ken.wolcott@med.ge.com> (raw)
In-Reply-To: <20031030232655.GA15004@invisible-island.net>

Hi Thomas;

  Hmmm...config.log in the gdb build directory shows nothing really meaningful 
unfortunately :-(

******************************************
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:581: checking host system type
configure:602: checking target system type
configure:620: checking build system type
configure:2697: checking for arm-arm9-linux-gnu-ar
configure:2769: checking for arm-arm9-linux-gnu-as
configure:2841: checking for arm-arm9-linux-gnu-dlltool
configure:2913: checking for arm-arm9-linux-gnu-ld
configure:2985: checking for arm-arm9-linux-gnu-nm
configure:3057: checking for arm-arm9-linux-gnu-ranlib
configure:3129: checking for arm-arm9-linux-gnu-windres
configure:3201: checking for arm-arm9-linux-gnu-objcopy
configure:3273: checking for arm-arm9-linux-gnu-objdump
configure:3354: checking for arm-arm9-linux-gnu-ar
configure:3426: checking for arm-arm9-linux-gnu-as
configure:3498: checking for arm-arm9-linux-gnu-dlltool
configure:3570: checking for arm-arm9-linux-gnu-ld
configure:3642: checking for arm-arm9-linux-gnu-nm
configure:3714: checking for arm-arm9-linux-gnu-ranlib
configure:3786: checking for arm-arm9-linux-gnu-windres
configure:3886: checking whether to enable maintainer-specific portions of 
Makefiles
******************************************

Ken

On Thursday 30 October 2003 17:26, Thomas Dickey wrote:
> On Thu, Oct 30, 2003 at 03:52:03PM -0600, Wolcott, Ken (MED, Compuware) 
wrote:
> > Hi;
> >
> >   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.
>
> There should be a config.log file in the gdb subdirectory that shows
> exactly what libraries were tried, and the corresponding -L options.
>
> This is what I'm using for djgpp for instance (to test cross-compiles of
> ncurses).
>
> #!/bin/sh
> # $Id: cfg-djgpp,v 1.2 2003/09/14 17:41:06 tom Exp $
> # configure to cross-compile ncurses for djgcc
> #
> # TODO: can I make it build with gnat?
> TARGET=i586-pc-msdosdjgpp
> TOOLS=/usr/local/compiler/cross/djgpp
> # export PATH=$TOOLS/bin:$PATH
> export AR=$TOOLS/bin/$TARGET-ar
> export RANLIB=$TOOLS/bin/$TARGET-ranlib
> export LD=$TOOLS/bin/$TARGET-ld
> export CC=djgcc
> export CXX=djgpp
> ./configure \
> 	--with-build-cc=gcc \
> 	--host=$TARGET \
> 	--target=$TARGET \
> 	$*


      parent reply	other threads:[~2003-10-31 14:43 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)
2003-10-31 18:41     ` Dan Kegel
     [not found] ` <20031030232655.GA15004@invisible-island.net>
2003-10-31 14:43   ` Wolcott, Ken (MED, Compuware) [this message]

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=200310310845.35490.ken.wolcott@med.ge.com \
    --to=ken.wolcott@med.ge.com \
    --cc=dickey@his.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