> If the CWD
> is /proc (so something without a Windows CWD), it seems to fall back to
> referring to '/a/b' again?!?
Oh, no. That makes me nearly impossible to determine whether a path is absolute
without getting the current PWD.
--
Yuyi Wang
--
Problem reports: https://cygwin.com/problem
On Wed, 11 Jun 2025, Jeremy Drake via Cygwin wrote:
> While making some tests for a path parser in rust
> (https://github.com/rust-lang/rust/pull/141864), an interesting corner
> case in Cygwin path handling came to light:
>
> Works:
> \\.\C:
> //.\C:
> //./C:\foo
>
> Doesn't work:
> //./C:
> //./
On 6/12/2025 1:28 PM, Bruno Haible via Cygwin wrote:
On Cygwin 3.6.3, I have the packages
gcc-core
gcc-g++
gcc-gdc
installed, all in version 11.5.0-1.
But the D compiler is dysfunctional: The attempt to compile any D source code
fails. E.g.:
$ echo > empty.d
$ gdc -c empty.c
d21: error
On Cygwin 3.6.3, I have the packages
gcc-core
gcc-g++
gcc-gdc
installed, all in version 11.5.0-1.
But the D compiler is dysfunctional: The attempt to compile any D source code
fails. E.g.:
$ echo > empty.d
$ gdc -c empty.c
d21: error: cannot find source code for runtime library file 'object
On 2025-06-11 18:57, Jeremy Drake via Cygwin wrote:
On Thu, 12 Jun 2025, Sam Edge via Cygwin wrote:
I would think that if you're building something against Cygwin, it's probably
best to assume it's POSIX where only forward-slash is special and not try to
second-guess.
This is unsafe, and actu
5 matches
Mail list logo
