From: Keith Seitz <keiths@redhat.com>
To: Doug Abbott <doug@intellimetrix.us>, gdb@sourceware.org
Subject: Re: gdb 9.2 won't build
Date: Tue, 8 Sep 2020 10:43:05 -0700 [thread overview]
Message-ID: <de5495a5-bd3a-48e1-550f-13a151cd7ce1@redhat.com> (raw)
In-Reply-To: <4d177e3a-4a2f-06e4-5b74-5ec982d45eda@intellimetrix.us>
On 9/8/20 9:59 AM, Doug Abbott wrote:
> 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?
Yes, you are definitely missing build dependencies. Since you're on
CentOS 7, try running:
# yum-builddep gdb
> 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".
An alternative is to try a DTS (developer toolset) release:
# yum install devtoolset-9-gdb
DTS9 comes with GDB 8.3. DTS10 (when available) will be based on GDB 9.2.
I am not very familiar with how the CentOS 7 software ecosystem works,
so if bad comes to worse, you can attempt to manually install a build
from the build system:
https://cbs.centos.org/koji/packageinfo?packageID=7466
I'm sure there's probably some repo for that, but since I don't use CentOS 7,
I don't know exactly what it is. Maybe
https://wiki.centos.org/AdditionalResources/Repositories/SCL ?
Keith
prev parent reply other threads:[~2020-09-08 17:43 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
2020-09-08 17:43 ` Keith Seitz [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=de5495a5-bd3a-48e1-550f-13a151cd7ce1@redhat.com \
--to=keiths@redhat.com \
--cc=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).