Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Tomasz Kłoczko via Gdb" <gdb@sourceware.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Eli Schwartz <eschwartz93@gmail.com>, Sam James <sam@gentoo.org>,
	gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Mon, 26 Feb 2024 00:29:38 +0000	[thread overview]
Message-ID: <CABB28CwhHkHXAbV3zRpLvegmqPRoG9iftU5R-xPa+M+1ex5yUA@mail.gmail.com> (raw)
In-Reply-To: <20240225233208.GD15517@gnu.wildebeest.org>

On Sun, 25 Feb 2024 at 23:32, Mark Wielaard <mark@klomp.org> wrote:

>
> Offlist you said that you didn't really got throttled because of those
> 8 packages you have that are hosted on sourceware none of them need
> many patches in the first place. So it isn't clear to me if we are
> actually discussing a real issue or if you are just worried that you
> could have an issue in theory.
>

So .. more than a decade of not updating gdb build automation to be able
use it with latest GNU autotools tooling is NOT THE REAL ISSUE?🤔
Really?
And .. sincerely thank you for your "argumentum ad hominem".

I found that gdb autoconf has some issue with ncurses detection when
ncurses source code is configured before compiling in some exact way.
I'm able to fix that but *I'm not able to test the result of that fix*
(before possible sending PR) because *I'm not able to regenerate all gdb
build automation .. because for more than decade that gdb automation update
has been postponed by any cost*.
Yes, ncurses code has changed in the last decade and now provides for
example full UTF-8 wide characters support.
In the last 3-4 years it offers as well a simpler source code setup which
so far is not widely used in any leading Linux distro.

Indirectly I've offered my help with updating that build automation as I'm
dealing with ac/am/lt *almost 30 years*.
Issue is that so far I don't see any WILL to work on that .. as it is not a
task for a single person and working on that alone would be WASTE OF TIME.
I have access only to Linux/x86_64 and Solari/OpenSolaris x86 and gdb
ac/am/lt automation needs to be correctly working on many asch and
operating systems.

Are you able to help me with ABOVE issue?🤔

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

  reply	other threads:[~2024-02-26  0:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 16:28 Tomasz Kłoczko via Gdb
2024-02-24 16:51 ` Sam James via Gdb
2024-02-24 17:15   ` Tomasz Kłoczko via Gdb
2024-02-24 17:21     ` Sam James via Gdb
2024-02-24 18:30       ` Tomasz Kłoczko via Gdb
2024-02-24 19:31         ` Mark Wielaard
2024-02-25  0:22           ` Tomasz Kłoczko via Gdb
2024-02-25  7:56             ` Mark Wielaard
2024-02-25  8:05             ` Eli Schwartz via Gdb
2024-02-25 10:40               ` Mark Wielaard
2024-02-25 21:19                 ` Eli Schwartz via Gdb
2024-02-25 21:50                   ` Tomasz Kłoczko via Gdb
2024-02-25 22:20                     ` Andreas Schwab
2024-02-25 23:32                     ` Mark Wielaard
2024-02-26  0:29                       ` Tomasz Kłoczko via Gdb [this message]
2024-02-26  0:46                         ` Eli Schwartz via Gdb
2024-02-26  0:55                           ` Tomasz Kłoczko via Gdb
2024-02-26 11:44                         ` Mark Wielaard
2024-02-26 12:13                           ` Tomasz Kłoczko via Gdb
2024-02-26  0:26                     ` Eli Schwartz via Gdb
2024-02-27 15:25         ` Tom Tromey
2024-02-27 16:37         ` Simon Marchi via Gdb
2024-02-27 17:33           ` Joseph Myers via Gdb
2024-02-27 17:42             ` Tom Tromey
2024-02-27 20:44             ` Tomasz Kłoczko via Gdb
2024-02-27 20:57               ` Tomasz Kłoczko via Gdb
2024-02-27 20:59               ` Sam James via Gdb
2024-02-26  0:58 ` Andrew Pinski via Gdb
2024-02-27 15:27   ` Tom Tromey

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=CABB28CwhHkHXAbV3zRpLvegmqPRoG9iftU5R-xPa+M+1ex5yUA@mail.gmail.com \
    --to=gdb@sourceware.org \
    --cc=eschwartz93@gmail.com \
    --cc=kloczko.tomasz@gmail.com \
    --cc=mark@klomp.org \
    --cc=sam@gentoo.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