From: Tom Kacvinsky via Gdb <gdb@sourceware.org>
To: Jan Beulich <jbeulich@suse.com>, Nick Clifton <nickc@redhat.com>,
GDB <gdb@sourceware.org>, Binutils <binutils@sourceware.org>
Subject: Re: Problems building gdbserver in binutils 2.46
Date: Mon, 9 Feb 2026 07:20:01 -0500 [thread overview]
Message-ID: <CAG_eJLc1UA4E03ZaUeDUEGOEZgQd5H16iOrOf0j=BPPMkNo_8g@mail.gmail.com> (raw)
In-Reply-To: <04de74ca-0fb9-4e8e-9d5a-41bb46269814@suse.com>
Hi,
On Mon, Feb 9, 2026 at 2:45 AM Jan Beulich <jbeulich@suse.com> wrote:
> On 08.02.2026 16:34, Tom Kacvinsky wrote:
> > Using CentOS 70 - which has glibc 2.17 and kernel 3.10.0 - and using the
> > tool chains
> >
> > GCC 12.1.0
> > binutils 2.39
> > libtool 2.47
> >
> > and then building binutil 2.46 from source without specifying
> > --disable-gdbserver, I got this build error
>
> Doesn't this point at a (long-standing) regression in how branching is
> done?
> Up to 2.24 gdb*/ weren't part of the branches, hence such an issue couldn't
> arise.
>
> I assume you would observe the same when building on the master branch;
> there
> the issue wants dealing with on the gdb side then; Cc-ing the correct list.
>
Yes, I switched to the master branch (from binutils-2_46) and the problems
exists
there, too.
So what I do being that I only want gas and ld, I configure with
../binutils-gdb/configure --prefix=${BINUTILS_PREFIX} \
--disable-gdb \
--disable-gdbserver \
--disable-gprof \
--disable-gprofng \
--enable-multilib
and then the build completes.
Tom
next prev parent reply other threads:[~2026-02-09 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG_eJLe_vuR93fE6H4hENPh3=R2XE72T2tL1ZaTnY93zW2J5-Q@mail.gmail.com>
2026-02-09 7:45 ` Jan Beulich via Gdb
2026-02-09 12:20 ` Tom Kacvinsky via Gdb [this message]
2026-02-09 14:43 ` Tom Kacvinsky via Gdb
2026-02-09 14:52 ` Andreas Schwab via Gdb
2026-02-09 14:54 ` Jan Beulich via Gdb
2026-02-09 15:24 ` Andreas Schwab via Gdb
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='CAG_eJLc1UA4E03ZaUeDUEGOEZgQd5H16iOrOf0j=BPPMkNo_8g@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=nickc@redhat.com \
--cc=tkacvins@gmail.com \
/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