Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb <gdb@sourceware.org>
To: Tom Kacvinsky <tkacvins@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: Problems building GC 18.1 on CentOS 7
Date: Sat, 3 Oct 2026 18:05:12 -0400	[thread overview]
Message-ID: <07d991a7-0605-4178-bc04-0fb0a4fd0f52@simark.ca> (raw)
In-Reply-To: <CAG_eJLdhGq=0+GML9UHZXq9JWk8zGdqUjJ=cvudNacyx+wTf=w@mail.gmail.com>



On 2026-10-03 15:18, Tom Kacvinsky via Gdb wrote:
> Hi,
> 
> I found a few issues with building GDB 18.1 on CentOS 7, using
> GCC 16.1.0 (which I had built from source)  They are two fold
> 
> 1. An issue with ./gdb/tui/tui-io.c using macro define(s) that the
> system curses headers don't provide.
> 
> 2. An issue with ptrace macro define(s) that are provided in glibc
> 2.18 or later, but not on CentOS 7, which is glibc 2.17 based.
> 
> I used Claude Opus 5 to generate a patch and manually inspected it.
> I am not sure what the GDB policy is for AI assisted patches.
> 
> I will get the exact compilation failures and the patch to the list on
> Monday.  To be honest, when it comes to the patch, I think I need to
> be mindful that I am building on Linux (via __linux__), using GCC
> (via __GNU__) and the glibc version is less than 2.18 using
> __GLIBC_PREREQ from features.h
> 
> Regards,
> 
> Tom

Hi Tom,

Could you please open a bug on Bugzilla?

https://sourceware.org/bugzilla/

If we are going to make a fix targetting 18.2, we will need a bug number
attached in any case.

Thanks,

Simon

  parent reply	other threads:[~2026-10-03 22:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 19:18 Tom Kacvinsky via Gdb
2026-10-03 20:47 ` Tom Kacvinsky via Gdb
2026-10-03 22:05 ` Simon Marchi via Gdb [this message]
2026-10-03 22:25   ` Tom Kacvinsky via Gdb
2026-10-04  1:55     ` Tom Kacvinsky via Gdb
2026-10-05 11:28 ` Guinevere Larsen via Gdb
2026-10-05 11:58   ` Tom Kacvinsky 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=07d991a7-0605-4178-bc04-0fb0a4fd0f52@simark.ca \
    --to=gdb@sourceware.org \
    --cc=simark@simark.ca \
    --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