Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: dje@google.com, gdb-patches@sourceware.org
Subject: Re: GDB 7.4 --with-python doesn't like d:/foo/bar
Date: Fri, 27 Jan 2012 10:02:00 -0000	[thread overview]
Message-ID: <83fwf1zdq3.fsf@gnu.org> (raw)
In-Reply-To: <20120127052515.GW31383@adacore.com>

> Date: Fri, 27 Jan 2012 09:25:15 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org, eliz@gnu.org
> 
> To me, the change would not be completely correct on Unix hosts,
> but I think that the chances of someone calling a local directory
> a single-letter followed by a colon are very small. So I think
> it's OK.

This is a standard way of Autoconf's catering to DOS and Windows
platforms.  You can see it at work elsewhere in the configure script,
because it's part of AC_PROG_PATH.  In fact, you can find it just a
few lines below the test that failed.

> I changed the expressions a bit replacing "[\\/]*" back into just "/"
> as originally used. Eli, would that still work for you?

Again, I think consistency with AC_PROG_PATH is better, even though a
case of a single backslash starting an absolute file name on Windows
is extremely rare.

Thanks.


  reply	other threads:[~2012-01-27  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  7:31 Eli Zaretskii
2012-01-27  5:34 ` Joel Brobecker
2012-01-27 10:02   ` Eli Zaretskii [this message]
2012-01-27 11:49     ` Joel Brobecker
2012-01-27 19:01       ` Doug Evans
2012-01-27 20:32         ` Eli Zaretskii

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=83fwf1zdq3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.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