1.1.8: bug in \\ handling in absolute fns

[Barubary]

> I get the results as mentioned.  This causes a newer gcc to fail to
> work, as libiberty uses \ to separate names in my toolchain, and TEMP
> is set by cygwin to /cygdrive/c/TEMP.  And this combination doesn't
> work, as mentioned above.  This worked in B19.  While libiberty could
> be made to not do this, or to canonicalize the pathnames, I feel that
> this is the wrong approach.

Does this have anything to do with why I can't compile GCC due to libiberty
not being found?

-- Barubary


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple