Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: GDB 9.0.90 available for testing
Date: Mon, 23 Dec 2019 07:54:00 -0000	[thread overview]
Message-ID: <20191223075408.GD11677@adacore.com> (raw)
In-Reply-To: <83r21440tk.fsf@gnu.org>

> > (1) make sure gdb_cv_cxx_std_thread is set to something, regardless of the code path taken
> > (2) wrap $db_cv_cxx_std_thread in quotes
> > 
> > Even if we do (1), it's good practice to do (2), in case the variable has spaces in it.
> > 
> > That code is in gdbsupport/common.m4.
> 
> Right.  I can fix common.m4, but I cannot regenerate configure, as I
> don't have the correct versions of autotools installed.  Should I fix
> common.m4, or would someone else want to do that?

One almost never has the correct versions of autotools pre-installed.
The distros tend to ship something close to the latest version that
was available at the time, and it rarely matches the version that
we are expected to use for each project. The only way I've found to
have the correct version was to build the various versions myself,
and update the PATH accordingly each time I need a set. More effort
than "it-just-works(tm)", but it's really not that bad. We don't change
the auto-tools versions all that often, and building those tools
just takes a few minutes each.

So, my recommendation if you want to control the pace at which this
is fixed, is to build your own set of auto-tools. On my end, I don't
think I'll have much time during the coming weeks, unfortunately.

-- 
Joel


  reply	other threads:[~2019-12-23  7:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 21:47 Joel Brobecker
2019-12-11 21:56 ` Joel Brobecker
2019-12-16 17:23 ` Eli Zaretskii
2019-12-16 17:38   ` Simon Marchi
2019-12-16 17:50     ` Eli Zaretskii
2019-12-23  7:54       ` Joel Brobecker [this message]
2019-12-16 18:52   ` Christian Biesinger via gdb-patches
2019-12-16 19:18     ` Eli Zaretskii
2019-12-16 19:36       ` Pedro Alves
2019-12-16 19:57         ` Eli Zaretskii
2019-12-16 20:37           ` Christian Biesinger via gdb-patches
2019-12-16 20:38           ` Pedro Alves
2019-12-17 17:25             ` Eli Zaretskii
2019-12-18 20:19   ` Christian Biesinger via gdb-patches
2019-12-19 15:00     ` Eli Zaretskii
2019-12-19 19:17       ` Christian Biesinger via gdb-patches
2019-12-19 19:38         ` Eli Zaretskii
2019-12-23  7:43           ` Joel Brobecker
2019-12-23 17:32             ` Eli Zaretskii
2019-12-24  3:53               ` Joel Brobecker
2019-12-24 15:30                 ` Eli Zaretskii
2020-01-17 20:56                   ` Christian Biesinger via gdb-patches
2020-01-17 21:09                     ` Eli Zaretskii
2019-12-23  8:01   ` Joel Brobecker
2019-12-23 13:56     ` Eli Zaretskii
2019-12-24  3:49       ` Joel Brobecker

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=20191223075408.GD11677@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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