From: Doug Abbott <doug@intellimetrix.us>
To: gdb@sourceware.org
Subject: gdb 9.2 won't build
Date: Tue, 8 Sep 2020 10:59:10 -0600 [thread overview]
Message-ID: <4d177e3a-4a2f-06e4-5b74-5ec982d45eda@intellimetrix.us> (raw)
Hi all,
I'm trying to build gdb 9.2 natively on a Linux x86_64 machine, a guest
running under VirtualBox on Windows 10. The linker is throwing a number
of "undefined reference" symbols like tputs and tgetflag which appear to
have something to do with ncurses and/or termcap.
I tried the configure command shown in the wiki under building natively,
adding --disable-tui because that fixed a different problem. I'm
guessing I'm missing a library, but which one?
The reason I'm going through this exercise is that gdb 7.6 that comes
with CentOS 7 won't read the python support functions for KGDB. It
complains about "missing attribute COMPLETE_EXPRESSION".
TIA for any help you can offer.
Doug
--
Doug Abbott
Principal Consultant, Intellimetrix
Linux for the Real World
575-590-2788
www.intellimetrix.us
next reply other threads:[~2020-09-08 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 16:59 Doug Abbott [this message]
2020-09-08 17:10 ` Joel Brobecker
2020-09-08 19:54 ` Doug Abbott
2020-09-08 17:43 ` Keith Seitz
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=4d177e3a-4a2f-06e4-5b74-5ec982d45eda@intellimetrix.us \
--to=doug@intellimetrix.us \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).