This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.4 --with-python doesn't like d:/foo/bar
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: dje at google dot com, gdb-patches at sourceware dot org
- Date: Fri, 27 Jan 2012 11:39:16 +0200
- Subject: Re: GDB 7.4 --with-python doesn't like d:/foo/bar
- References: <E1RqJbR-00068v-M2@fencepost.gnu.org> <20120127052515.GW31383@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.