From: Levente <leventelist@gmail.com>
To: binutils@sourceware.org
Subject: Build failure on Debian stable
Date: Sat, 17 Feb 2024 16:11:41 +0100 [thread overview]
Message-ID: <f0dec8f8-ae92-4d97-9a87-7b027f5055be@gmail.com> (raw)
Hi,
I'm trying to build binutils and gdb on Debian stable.
I do this:
mkdir test_build
cd test_build
../configure
make
I get 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
make[2]: Leaving directory
'/home/lev/git/library/software/scripts/avr_toolchain_build/binutils-gdb/test_build/gdb'
make[1]: *** [Makefile:13473: all-gdb] Error 2
make[1]: Leaving directory
'/home/lev/git/library/software/scripts/avr_toolchain_build/binutils-gdb/test_build'
make: *** [Makefile:1032: all] Error 2
My environment is this:
gcc --version
gcc (Debian 12.2.0-14) 12.2.0
uname -a
Linux athena 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1
(2024-02-01) x86_64 GNU/Linux
I'm not sure I miss something.
If I disable gdb, it compiles.
Thanks for your help,
Levente
--
Levente Kovacs
Senior Electronic Engineer
W: http://levente.logonex.eu
next reply other threads:[~2024-02-17 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 15:11 Levente [this message]
2024-02-17 16:59 ` H.J. Lu
2024-02-19 11:30 ` Nick Clifton
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=f0dec8f8-ae92-4d97-9a87-7b027f5055be@gmail.com \
--to=leventelist@gmail.com \
--cc=binutils@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).