From: Doug Abbott <doug@intellimetrix.us>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 9.2 won't build
Date: Tue, 8 Sep 2020 13:54:22 -0600 [thread overview]
Message-ID: <842589e6-7085-0533-7e15-a7e279b3c123@intellimetrix.us> (raw)
In-Reply-To: <20200908171048.GE18641@adacore.com>
Thanks for the hint Joel. I had to install the ncurses-devel and texinfo
packages and then it built.
Doug
On 9/8/2020 11:10 AM, Joel Brobecker wrote:
>> 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".
> Try maybe forcing the use of ncuses by configuring GDB --with-curses?
> You might get an error if you don't have the ncurses headers installed;
> if that happens, install the ncurses dev package, and then try again.
>
--
Doug Abbott
Principal Consultant, Intellimetrix
Linux for the Real World
575-590-2788
www.intellimetrix.us
next prev parent reply other threads:[~2020-09-08 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 16:59 Doug Abbott
2020-09-08 17:10 ` Joel Brobecker
2020-09-08 19:54 ` Doug Abbott [this message]
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=842589e6-7085-0533-7e15-a7e279b3c123@intellimetrix.us \
--to=doug@intellimetrix.us \
--cc=brobecker@adacore.com \
--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).