insight/4: ppc simulator in insight fails to compile

insight/4: ppc simulator in insight fails to compile

[kjoutwater]

>Number:         4
>Category:       insight
>Synopsis:       ppc simulator in insight fails to compile
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 11 17:03:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     kjoutwater@west.raytheon.com
>Release:        insight-19990809
>Organization:
>Environment:
uname -a -> HP-UX cae779 B.10.20 A 9000/782

powerpc-elf cross built with gcc-2.95, newlib-1.8.1, binutils-2.9.1
insight-19990809 configured with: 
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
../insight-19990809/configure --host=hppa2.0-hp-hpux10.20 --prefix=/users/cae779/vac4050/usr/local --target=powerpc-elf -v --norecursion 
>Description:
make[2]: Entering directory `/local/users/vac4050/pkgs/ppc_cross/build-insight/sim/ppc'
gcc -c -O2 -W -Wall -DDEFAULT_INLINE=INLINE_LOCALS     -DWITH_HOST_BYTE_ORDER=BIG_ENDIAN -DWITH_SMP=5              -DHAVE_TERMIOS_STRUCTURE    -DHOST_HPPAHPUX  -I. -I../../../insight-19990809/sim/ppc -I../../../insight-19990809/sim/ppc/../../include -I../../bfd -I../../../insight-19990809/sim/ppc/../../bfd -I../../gdb -I../../../insight-19990809/sim/ppc/../../gdb  -I../../../insight-19990809/sim/ppc/../../gdb/config -I../../../insight-19990809/sim/ppc/../../mmalloc ../../../insight-19990809/sim/ppc/bits.c
../../../insight-19990809/sim/ppc/bits.c: In function `MASKED':
../../../insight-19990809/sim/ppc/bits.c:53: internal error--insn does not satisfy its constraints:
(jump_insn 142 39 41 (parallel[ 
            (set (pc)
                (label_ref 140))
            (set (reg:SI 88 SAR)
                (reg:SI 19 %r19))
        ] ) 270 {decrement_and_branch_until_zero+5} (nil)
    (expr_list:REG_BR_PRED (const_int 14 [0xe])
        (nil)))
make[2]: *** [bits.o] Error 1
make[2]: Leaving directory `/local/users/vac4050/pkgs/ppc_cross/build-insight/sim/ppc'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/local/users/vac4050/pkgs/ppc_cross/build-insight/sim'
make: *** [all-sim] Error 2
>How-To-Repeat:
build for powerpc-elf (??)
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From jsm@cygnus.com Wed Aug 11 17:56:00 1999
From: jsm@cygnus.com
To: insight-prs@sourceware.cygnus.com, jsm@cygnus.com, kjoutwater@west.raytheon.com, nobody@sourceware.cygnus.com
Subject: Re: insight/4
Date: Wed, 11 Aug 1999 17:56:00 -0000
Message-id: <19990812005651.16337.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00001.html
Content-length: 630

Synopsis: ppc simulator in insight fails to compile

Responsible-Changed-From-To: unassigned->jsm
Responsible-Changed-By: jsm
Responsible-Changed-When: Wed Aug 11 17:56:51 1999
Responsible-Changed-Why:
    Me.
State-Changed-From-To: open->closed
State-Changed-By: jsm
State-Changed-When: Wed Aug 11 17:56:51 1999
State-Changed-Why:
    This is a GCC problem, not a GDB problem.  Please report
    this to the GCC project.  They have instructions for reporting
    bugs, here is the URL:
    
    	http://egcs.cygnus.com/onlinedocs/gcc_8.html#SEC136

http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?cmd=view&database=insight&pr=4
>From jsm@cygnus.com Wed Aug 11 22:23:00 1999
From: Jason Molenda <jsm@cygnus.com>
To: jsm@cygnus.com
Cc: insight-prs@sourceware.cygnus.com
Subject: Re: insight/4
Date: Wed, 11 Aug 1999 22:23:00 -0000
Message-id: <19990812052300.3692.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00002.html
Content-length: 387

The following reply was made to PR insight/4; it has been noted by GNATS.

From: Jason Molenda <jsm@cygnus.com>
To: insight-gnats@sourceware.cygnus.com
Cc:  
Subject: Re: insight/4
Date: Wed, 11 Aug 1999 22:21:41 -0700

 By the way, I talked to our simulator dude and he suggested that
 you may be able to work around the compiler bug by configuring with
 --disable-sim-inline.
 
 Jason
>From keith@baltimore.ie Mon Aug 16 16:43:00 1999
From: keith@baltimore.ie
To: insight-gnats@sourceware.cygnus.com
Subject: insight/5: inconvenient final behaviour and argument setting
Date: Mon, 16 Aug 1999 16:43:00 -0000
Message-id: <19990816233807.1237.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00003.html
Content-length: 986

>Number:         5
>Category:       insight
>Synopsis:       inconvenient final behaviour and argument setting
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 16 16:43:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Keith Brady <keith@baltimore.ie>
>Release:        19990809
>Organization:
>Environment:
Linux RH 6.0 (2.2.x kernel)
>Description:
The final source window left open after the program terminates is
the one where the exit() (or whatever) happened not the
last to receive user input. This is inconvenient especially
when combined with the lack of a most-recent-windows
feature.

In addition, it is not clear how to provide command-line
arguments.

These problems don't detract from the fact that it is a
cool product which is impressively fast.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From jeff.walker@autozone.com Wed Aug 18 13:13:00 1999
From: jeff.walker@autozone.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/6: compile problem
Date: Wed, 18 Aug 1999 13:13:00 -0000
Message-id: <19990818200732.8376.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00004.html
Content-length: 879

>Number:         6
>Category:       insight
>Synopsis:       compile problem
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 18 13:13:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Jeff Walker
>Release:        19990816
>Organization:
>Environment:
AIX 4.3.2.0
>Description:
I after "configure", I issue "make gdb-all"

I get:

        cc -c -g     -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode -I./../readline/..  -I../bfd -I./../bfd  -I./../include  -I../intl -I./../intl -I./tui -DGDBTK  gdbarch.c
"gdbarch.c", line 247.3: 1506-045 (S) Undeclared identifier generic_get_saved_register.
make: 1254-004 The error code from the last command is 1.
>How-To-Repeat:

>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted:
>From edA-qa@disemia.com Mon Aug 23 19:13:00 1999
From: edA-qa@disemia.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/7: Win98 make/sh error
Date: Mon, 23 Aug 1999 19:13:00 -0000
Message-id: <19990824021125.30219.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00005.html
Content-length: 666

>Number:         7
>Category:       insight
>Synopsis:       Win98 make/sh error
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 23 19:13:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     edA-qa@disemia.com
>Release:        Latest
>Organization:
>Environment:
Win98
>Description:
using SH/BASH to run the configure script in Windows98 causes a page fault -- SH.EXE is causing the fault.

>How-To-Repeat:
run "sh configure" in the base directory of the extracted files
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From pmueller@decrc.abb.de Fri Aug 27 00:33:00 1999
From: pmueller@decrc.abb.de
To: insight-gnats@sourceware.cygnus.com
Subject: insight/8: can't debug multithreading applications
Date: Fri, 27 Aug 1999 00:33:00 -0000
Message-id: <19990827072649.12423.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00006.html
Content-length: 790

>Number:         8
>Category:       insight
>Synopsis:       can't debug multithreading applications
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 27 00:33:04 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     pmueller@decrc.abb.de
>Release:        19990823
>Organization:
>Environment:
Linux Redhat 6, pthreads
>Description:
When I try to create a new thread I got the message:
"Unknown signal". When I continue running afterwards, the
gdb hang.
>How-To-Repeat:
Start gdb and try to run any multithreaded app on linux.
>Fix:
gdb "4.17.0.11 with linux support" is able to debug 
multithreaded apps.
>Release-Note:
>Audit-Trail:
>Unformatted:
>From l.le_huerou_kerisel@edixia.fr Tue Sep 07 00:03:00 1999
From: l.le_huerou_kerisel@edixia.fr
To: insight-gnats@sourceware.cygnus.com
Subject: insight/9: make error (permission denied)
Date: Tue, 07 Sep 1999 00:03:00 -0000
Message-id: <19990907070111.24847.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00007.html
Content-length: 6520

>Number:         9
>Category:       insight
>Synopsis:       make error (permission denied)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 07 00:03:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     l.le_huerou_kerisel@edixia.fr
>Release:        19990830
>Organization:
>Environment:
PC / Win95 Service Pack 1
>Description:
This is a drop of a plain text in Wordpad. So if not readable, i send it to your mail insight@... too.

I work on a PC/Win95 Service Pack 1

After installing cygwin in c:\cygnus and unpacking insight-19990830 in c:\cygnus too, i ran :
  configure --target=m68k-coff --prefix=/cygnus/insight
from the directory /cygnus/insight-19990830, to build a cross 68k version of insight.

This step first failed and after a registry cleanup it worked to the end.

Now I run the same command :
  configure --target=m68k-coff --prefix=/cygnus/insight

configure now seems to end correctly with this last outputs (screen copy from BASH window) :
################ BEGIN ##################################
loading cache ../../../config.cache
checking host system type... i586-pc-cygwin32
checking target system type... m68k-unknown-coff
checking build system type... i586-pc-cygwin32
checking how to run the C preprocessor... (cached) gcc -E
checking for pthread.h... no
updating cache ../../../config.cache
creating ./config.status
creating Makefile
creating config.h
configuring in gdb.trace
running /bin/sh ./configure  --host=i586-pc-cygwin32 --target=m68k-coff --prefix
=/cygnus/insight --cache-file=../../../config.cache --srcdir=.
loading cache ../../../config.cache
checking host system type... i586-pc-cygwin32
checking target system type... m68k-unknown-coff
checking build system type... i586-pc-cygwin32
updating cache ../../../config.cache
creating ./config.status
creating Makefile
configuring in gdb.gdbtk
running /bin/sh ./configure  --host=i586-pc-cygwin32 --target=m68k-coff --prefix
=/cygnus/insight --cache-file=../../../config.cache --srcdir=.
loading cache ../../../config.cache
checking host system type... i586-pc-cygwin32
checking target system type... m68k-unknown-coff
checking build system type... i586-pc-cygwin32
updating cache ../../../config.cache
creating ./config.status
creating Makefile
Configuring etc...
loading cache ../config.cache
checking for a BSD compatible install... (cached) /CYGNUS/CYGWIN~1/H-I586~1/BIN/
install -c
updating cache ../config.cache
creating ./config.status
creating Makefile
Configuring utils...
Created "Makefile" in /cygnus/insight-19990830/utils
Configuring spu...
Created "Makefile" in /cygnus/insight-19990830/utils/spu
BASH.EXE-2.02$
################# END ###################################

Then I run make :
  make

make fails with this last outputs (screen copy from BASH window) :
################ BEGIN ##################################
for i in coff-m68k.lo cofflink.lo versados.lo ieee.lo cpu-m68k.lo  ; do \
  case " $f " in \
    *" $i "*) ;; \
    *) f="$f $i" ;; \
  esac ; \
done ; \
echo $f > tofiles
/bin/sh ./../move-if-change tofiles ofiles
touch stamp-ofiles
/bin/sh ./libtool --mode=link gcc  -g -O2 -W -Wall  -o libbfd.la -rpath /cygnus/
insight/lib -release 2.9.5  archive.lo archures.lo bfd.lo cache.lo coffgen.lo co
refile.lo format.lo init.lo libbfd.lo opncls.lo reloc.lo section.lo syms.lo targ
ets.lo hash.lo linker.lo srec.lo binary.lo tekhex.lo ihex.lo stabs.lo stab-syms.
lo `cat ofiles`
Usage: cygpath [-p|--path] (-u|--unix)|(-w|--windows) filename
  -u|--unix     print Unix form of filename
  -w|--windows  print Windows form of filename
  -p|--path     filename argument is a path
libtool: link: warning: undefined symbols not allowed in i586-pc-cygwin32 shared
 libraries
mkdir .libs
lib /OUT:.libs/libbfd.lib  archive.o archures.o bfd.o cache.o coffgen.o corefile
.o format.o init.o libbfd.o opncls.o reloc.o section.o syms.o targets.o hash.o l
inker.o srec.o binary.o tekhex.o ihex.o stabs.o stab-syms.o coff-m68k.o cofflink
.o versados.o ieee.o cpu-m68k.o
lib: permission denied
make[3]: *** [libbfd.la] Error 127
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive-am] Error 2
make: *** [all-bfd] Error 2
BASH.EXE-2.02$ 
##### END ########

I then retrie make from here :
make fails again with  the same last outputs (screen copy from BASH window) :
##### BEGIN #######
Making all in doc
make[3]: Nothing to be done for `all'.
make[1]: Nothing to be done for `all'.
make  all-recursive
Making all in doc
make[3]: Nothing to be done for `all'.
Making all in po
make[3]: Nothing to be done for `all'.
/bin/sh ./libtool --mode=link gcc  -g -O2 -W -Wall  -o libbfd.la -rpath /cygnus/
insight/lib -release 2.9.5  archive.lo archures.lo bfd.lo cache.lo coffgen.lo co
refile.lo format.lo init.lo libbfd.lo opncls.lo reloc.lo section.lo syms.lo targ
ets.lo hash.lo linker.lo srec.lo binary.lo tekhex.lo ihex.lo stabs.lo stab-syms.
lo `cat ofiles`
Usage: cygpath [-p|--path] (-u|--unix)|(-w|--windows) filename
  -u|--unix     print Unix form of filename
  -w|--windows  print Windows form of filename
  -p|--path     filename argument is a path
libtool: link: warning: undefined symbols not allowed in i586-pc-cygwin32 shared
 libraries
rm -fr .libs/libbfd.la .libs/libbfd.* .libs/libbfd-2.9.5.*
lib /OUT:.libs/libbfd.lib  archive.o archures.o bfd.o cache.o coffgen.o corefile
.o format.o init.o libbfd.o opncls.o reloc.o section.o syms.o targets.o hash.o l
inker.o srec.o binary.o tekhex.o ihex.o stabs.o stab-syms.o coff-m68k.o cofflink
.o versados.o ieee.o cpu-m68k.o
lib: permission denied
make[3]: *** [libbfd.la] Error 127
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive-am] Error 2
make: *** [all-bfd] Error 2
BASH.EXE-2.02$
######## END ########

Exit from bash, cleaning registry again and running make again does not solve the problem.
Regclean does not report registry error after this make process.


I have kept the directory structure of the cygnus dir at this point (dir /s > dirstr.txt under windows MS-DOS console) if needed (joined to the mail). Missing items or processing dates of the output files could perhaps help.

Note that we have configured and make and tested  the gcc m68k-coff target before all this (cross gcc+gdb tested). This to say that another building process works correctly .

>How-To-Repeat:
Seems rather to be linked to my working context
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From villa@txt.it Tue Sep 07 00:13:00 1999
From: villa@txt.it
To: insight-gnats@sourceware.cygnus.com
Subject: insight/10: Step / Next / Continue Buttons activation/deactivation
Date: Tue, 07 Sep 1999 00:13:00 -0000
Message-id: <19990907071124.25822.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00008.html
Content-length: 1074

>Number:         10
>Category:       insight
>Synopsis:       Step / Next / Continue Buttons activation/deactivation
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 07 00:13:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     villa@txt.it
>Release:        Insight 19990830
>Organization:
>Environment:
Host: pc-cygwin32
Target: m68k 
>Description:
When non connected to remote target (via TCP), the "next,
step, .." buttons are disabled (and this is correct)
When I connect to target remote, they are activated (right)
Then I disconnect, and the buttons remain activated (WRONG!)
When I connect again, they are disactivated ! (WRONG)
>How-To-Repeat:
- connect to target remote (TCP)
- after connecting, disconnect without performing any other
action
- try connecting / disconnecting again.....
>Fix:
don't know but the problem is surely in the .tcl files,
not in the GDB itself
>Release-Note:
>Audit-Trail:
>Unformatted:
>From shukypATdigital-links.co.il Wed Sep 15 01:53:00 1999
From: shukyp AT digital-links.co.il
To: insight-gnats AT sourceware.cygnus.com
Cc: shukyp AT gadline.co.il
Subject: insight/11: debugger operation
Date: Wed, 15 Sep 1999 01:53:00 -0000
Message-id: <19990915084802.16542.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00009.html
Content-length: 1277

>Number:         11
>Category:       insight
>Synopsis:       debugger operation
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 15 01:53:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Shuky Persky
>Release:        Code Fusion ver. 1.0
>Organization:
>Environment:
Linux - Redhat 5.2
>Description:
1st, why do I have to nevigate that long until raching this entry, please locate it in the support main page.

2nd (to the point) - I debug a multi-thread application. 
As loading the program, the Control drop menu, is disabled.

So what is left is to hit the 'Run' botton. this creates 
a msg "Cannot determine thread signal numbber ... spurios signal".

In addition as my code invokes an OS library API -thread_create (...), the debugger goes to assembly code. 
I asked the debugger to step over, but it rathers to step in.

SO please help me. This is urgent. My application needs the 
threads debugging capability (thats why I bought this product), but for unfamiliar reasons it fails doing the VERY
basic ecpectations of a debugger.
>How-To-Repeat:
What does this mean ???
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From tillATdasburo.com Fri Sep 17 12:13:00 1999
From: till AT dasburo.com
To: insight-gnats AT sourceware.cygnus.com
Subject: insight/12: target remote COMx often does not work
Date: Fri, 17 Sep 1999 12:13:00 -0000
Message-id: <19990917191153.23737.qmail@egcs.cygnus.com>
X-SW-Source: 1999-q3/msg00010.html
Content-length: 1118

>Number:         12
>Category:       insight
>Synopsis:       target remote COMx often does not work
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 17 12:13:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     till@dasburo.com
>Release:        insight-19990727
>Organization:
>Environment:
m68k-coff cross on Windows NT SP 4, Windows 95
>Description:
serial communication hangs. Program is only interruptable
if target sends a lot of output.

cat /dev/com2 works (with wrong baudrate)
>How-To-Repeat:
1) Start target, let it run into breakpoint. Start Debugger
with options -nw -b 38400 xxx.coff. enter target remote COM2.
-> Message:
1001 (0) fhandler_serial::tcsetattr:CommTimeout failed
set_tty_state failed: Bad file number
-> hangs forever
set remotetimeout or set watchdog does not help

2) Start debugger without -nw option.
select target settings.
connect to target.
-> no message, hangs forever
>Fix:
unfortunately none
>Release-Note:
>Audit-Trail:
>Unformatted:
>From philip@emarq.com Thu Oct 14 16:43:00 1999
From: philip@emarq.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/13: insight hangs on some pre-set undeletable breakpoint 
Date: Thu, 14 Oct 1999 16:43:00 -0000
Message-id: <19991014234132.11593.qmail@sourceware.cygnus.com>
X-SW-Source: 1999-q4/msg00000.html
Content-length: 1212

>Number:         13
>Category:       insight
>Synopsis:       insight hangs on some pre-set undeletable breakpoint
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 14 16:43:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Philip Fleischer
>Release:        insight-19991011 and insight-19991004
>Organization:
>Environment:
red hat 6
>Description:
I enter gdb a.out and the source window opens up
but there is dark blue over one of the source lines,
I did not set this as a bp and there is no little
red square
But when I hit run, execution gets to that point
and waits forever with a little red octagon stop sign 

I got further debugging before but once I got to what
I describe above, I can't get passed it
>How-To-Repeat:
I don't know how you can repeat this but it always happens
to me even if I make another a.out from another source
I have downloaded and installed another snapshot and it 
still happens
>Fix:
there is probably an explanation you can give me and something
I can do different so this won't happen
>Release-Note:
>Audit-Trail:
>Unformatted:
>From mthibault@rocx.com Tue Nov 16 09:23:00 1999
From: mthibault@rocx.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/14: configure fails - could not find term library
Date: Tue, 16 Nov 1999 09:23:00 -0000
Message-id: <19991116171938.19490.qmail@sourceware.cygnus.com>
X-SW-Source: 1999-q4/msg00001.html
Content-length: 827

>Number:         14
>Category:       insight
>Synopsis:       configure fails - could not find term library
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 16 09:23:00 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Mark Thibault
>Release:        1.278 (insight-19991108)
>Organization:
>Environment:
RedHat Linux 6.1
>Description:
I get the error 'Could not find a term library' during 
'checking for tgetent ...'. This is after the 'Configuring 
gdb...' line
>How-To-Repeat:
It repeats on one machine by running configure again, but 
it succeeded on another. I have recheck and reinstalled the
term libraries that I know of.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: