Re: Problems building gdbserver in binutils 2.46

Hi,

On Mon, Feb 9, 2026 at 7:20 AM Tom Kacvinsky <[email protected]> wrote:

> Hi,
>
> On Mon, Feb 9, 2026 at 2:45 AM Jan Beulich <[email protected]> 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.
>
>
I did note that PTRACE_GET_THREAD_AREA is available in glibc 2.31 (on my
openSUSE Leap 15.5 VM).  Not sure which glibc version introduced that. If
Google's AI overview can be trusted, it says that PTRACE_TYPE_ARG1 is
supposed to be auto-detected/set by configure.  I looked at the configure
scripts and did not see a "#define PTRACE_TYPE_ARG1 ..."
Tom