Backslashes in configure script - is this a bug?

[Roger Cruz <RogerC@Ignitus.com>]

In trying to figure out why final link is failing, I started to examine
the output of ./configure at the top level of GDB 4.18 using the bash
shell provided with CygWin B20.1 and I find that there is an error:

+
c:\PROGRA~1\cygnus\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\eg
cs-2.91.57\..\..\..\..\i586-cygwin32\bin\ld.exe -v
+ egrep (GNU|with BFD)
c:\PROGRA~1\cygnus\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\eg
cs-2.91.57\..\..\..\..\i586-cygwin32\bin\ld.exe: permission denied

The peculiar thing is that this is the only line that uses DOS's back
slash for dir separator and the "C:" rather than //c/progra~1 like all
the other lines are doing.  I searched in the ./configure script for the
origins of this line and I believe it comes from line 1332 where ac_prog
is being set to the value returned by CC -print-prog-name.  The value
returned is in DOS notation and it does not appear to be changed to
unix's.

Why is this happening in my environment?  Has anyone else seen this type
of problem?  Please help.  I've been trying to get GDB build for the
last 3 days without any luck and I'm going to be force to abandon using
it soon.

Thanks.
Roger

ac_prog=ld
if test "$ac_cv_prog_gcc" = yes; then
  # Check if gcc -print-prog-name=ld gives a path.
  echo $ac_n "checking for ld used by GCC""... $ac_c" 1>&6
echo "configure:1332: checking for ld used by GCC" >&5
  ac_prog=`($CC -print-prog-name=ld) 2>&5`
  case "$ac_prog" in