Absolute paths in BFD
Chris Faylor
cgf@cygnus.com
Sat Apr 22 13:34:00 GMT 2000
On Sat, Apr 22, 2000 at 04:15:44PM -0400, Timothy Wall wrote:
>I've noticed quite a few instances in BFD where absolute paths are
>tested by expecting the first character to be '/' (grep for "== '/'" to
>see how often this is done). This test breaks under cygwin when drive
>letters are used as part of a pathname.
Just to pick nits, it's actually a problem under Windows, not Cygwin
specifically. Cygwin tries to mask the x:\ madness.
>There should probably be a bfd function for absolute path-ness, and that
>called instead of explicitly doing the leading slash test.
>
>I was about to make a small patch when I realized that this check is
>going on in many more places than the bug I was tracking.
I seem to be fighting a losing battle to convince everyone to just use
Cygwin POSIX-style pathnames, so this seems like a great idea for
the MS-DOS pathname purists. It would be nice to make bfd able to
understand at least the x:/foo/bar (i.e., without the backslashes)
version of MS-DOS syntax.
I don't think we want to go as far as allowing '\' as a path separator,
though.
cgf
More information about the Binutils
mailing list