From: Levente <leventelist@gmail.com>
To: gdb@sourceware.org
Subject: Building GDB
Date: Tue, 20 Feb 2024 00:00:36 +0100 [thread overview]
Message-ID: <3a1c2a28-d703-48ae-ae70-6354a75dfd9e@gmail.com> (raw)
Hi all,
I'm putting together a toolchain for AVR micro-controllers, and want to
build GDB without binutils. I checked out the source, and when I'm on
the binutils-2_42 tag, the build fails with this:
CXX tui/tui-command.o
In file included from ../../gdb/tui/tui-data.h:28,
from ../../gdb/tui/tui-command.c:24:
../../gdb/../gdbsupport/gdb-checked-static-cast.h: In instantiation of
‘T gdb::checked_static_cast(V*) [with T = tui_cmd_window*; V =
tui_win_info]’:
../../gdb/tui/tui-command.c:65:15: required from here
../../gdb/../gdbsupport/gdb-checked-static-cast.h:63:14: error: cannot
convert from pointer to base class ‘tui_win_info’ to pointer to derived
class ‘tui_cmd_window’ because the base is virtual
63 | T result = static_cast<T> (v);
| ^~~~~~~~~~~~~~~~~~
make[2]: *** [Makefile:1930: tui/tui-command.o] Error 1
So I decided to build gdb and binutils separately from different
commits. I can disable GDB by specifying --without-gdb.
The question is, how can I build GDB without binutils?
So here is what I want to do:
check out binutils-2_42
configure/build/install binutils
clean the repo
chec out gdb-14.1-release
configure/build/install gcc
How can I do this?
Thanks,
Lev
--
Levente Kovacs
Senior Electronic Engineer
W: http://levente.logonex.eu
next reply other threads:[~2024-02-19 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 23:00 Levente [this message]
2024-02-19 23:55 ` Tom Kacvinsky
2024-02-21 16:03 ` Guinevere Larsen
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 13:38 Building gdb Tim Bedding
2005-10-20 13:45 ` sjhill
2005-10-20 14:06 ` Mark Kettenis
2005-10-20 13:49 ` Eli Zaretskii
2005-10-20 13:53 ` Daniel Jacobowitz
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=3a1c2a28-d703-48ae-ae70-6354a75dfd9e@gmail.com \
--to=leventelist@gmail.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).